Login timed out from Socket Listener?

Does anyone have a clue on why I got the following error?
Thanks.
Mon Sep 18 18:50:42 PDT 2000:<W> <ListenThread> Connection rejected: 'Login timed out after: '5000' ms on socket: 'Socket[addr=qelab3.ariba.com/10.10.16.104,port=1298,localport=8001]''

We do not support ssl between plugins and weblogic yet. Currently if you send a https request, plugins will just downgrade them to http.
Srikant, [email protected], http://weblogic.bea.com/, etc.
Prabhu Kannan wrote:
Hi,
I am facing the same problem. I have configured NSAPI plugin in our NES server and the WebLogic 5.1. I am trying to connect to Weblogic through the SSL port. It times out. I see the following message in the NES log.
[08/Nov/2000:15:51:56] failure (16491): for host 10.203.3.78 trying to GET /weblogic/index.html, wl-proxy reports: Error reading WebLogic Response from 10.203.1.226:7021 at line 764 of proxy.cpp, errMsg='File not found'
Both the web server and weblogic have SSL certificates installed in them.
Can you give me some ideas as to how to get this to work?
Thanks,
Prabhu
Srikant Subramaniam <[email protected]> wrote:
From an earlier posting:
This sounds like a slow client to me. Specifically the client isn't sending enough data (something like 7 bytes) within the first 5 seconds for the server to determine which protocol the
client is using. I believe that future versions of the server squelch this message by default because logging errors caused by poorly behaving clients seems to cause a good deal of noise
in the logs, especially when running a public site.
the client timeout parameter can be increased, see:
http://www.weblogic.com/docs51/admindocs/properties.html#login
Srikant, [email protected], http://weblogic.bea.com/, etc.
John Xiao wrote:
Does anyone have a clue on why I got the following error?
Thanks.
Mon Sep 18 18:50:42 PDT 2000:<W> <ListenThread> Connection rejected: 'Login timed out after: '5000' ms on socket: 'Socket[addr=qelab3.ariba.com/10.10.16.104,port=1298,localport=8001]''

Similar Messages

Re: Connection Rejected:Login Timed Out

This sounds like a slow client to me. Specifically the client isn't sending
enough data within the first 9 seconds for the server to determine which
protocol the client is using.
Srikant, [email protected], http://weblogic.bea.com/, etc.
Ajit wrote:
"Hi, I went through the various versions of Login Timed Out problems.This is my version. My Web server currently running on Weblogic Web Server 5.1.0 with service pack 9 is shutting down frequently.My server platform is SUN SOLARIS 2.6 5/98. The following messages reflect in the weblogic.log Thu Aug 02 08:49:52 EDT 2001:<W> <ListenThread> Connection rejected: 'Login timed out after 9000 msec. The socket came from [host=147.154.232.3,port=19431,localport=80] See property weblogic.login.readTimeoutMillis to increase of decrease timeout. See property weblogic.login.logReadTimeoutsProp to turn off these log messages.'Thu Aug 02 08:50:13 EDT 2001:<W> <ListenThread> Connection rejected: 'Login timed out after 9000 msec. The socket came from [host=147.154.232.5,port=10656,localport=80] See property weblogic.login.readTimeoutMillis to increase of decrease timeout. See property weblogic.login.logReadTimeoutsProp to turn off these log messages.'Thu Aug 02 09:23:18 EDT
2001:<!> <SSLListenThread> **** The WebLogic Server is no longer listening for connections.Thu Aug 02 09:23:18 EDT 2001:<!> <SSLListenThread> **** You should probably restart it.Thu Aug 02 09:23:18 EDT 2001: <WebLogicServer> Server shutdown by systemThu Aug 02 09:23:18 EDT 2001: <WebLogicServer> Server shutdown commencing NOWThu Aug 02 09:23:18 EDT 2001:<A> <ListenThread> ListenThread.run() failed:java.lang.ThreadDeathThu Aug 02 09:23:18 EDT 2001:<!> <ListenThread> **** The WebLogic Server is no longer listening for connections.Thu Aug 02 09:23:18 EDT 2001:<!> <ListenThread> **** You should probably restart it.Thu Aug 02 09:23:18 EDT 2001: <WebLogicServer> Server shutdown by systemThu Aug 02 09:23:19 EDT 2001: <HTTP> Destroying servlets in default servlet context.Thu Aug 02 09:23:19 EDT 2001: <ServletContext-General> proxy: destroyThu Aug 02 09:23:19 E

hi srikanth i am facing some problem in weblogic for a particular port.weblogic
is shutting down for that port .this port
is configured for SSL.
when i have reviewed the logs i could trace
following error.i dont know whether this error is linked to the shutting down of weblogic.
ERROR:on Apr 08 13:30:36 CEST 2002:<W> <SSLListenThread> Connection rejected: 'Login
timed out after: '25000' ms on socket: 'Socket[addr=192.193.118.137/192.193.118.
137,port=33280,localport=7003}''
Each and everytime restarting the weblogic
instance is not a proper solution so please
let me know what can i do for this weblogic
shutting down abnormally.
waiting for ur reply
Best Regards
Surender
Wipro Limited.

WEBLOGIC 5.1SP9 : ListenThread Connection rejected: 'Login timed out after 5000 msec.

I'm running WL Express 5.1SP9 on a NT 4 server, Oracle 8.1.7 and an j2EE
application from an editor.
With the previous version of the application i wasn't having any problem,
since I installed the new version in the same environnement, I'm getting the
message when running the application :
"<E> <ServletContext-General> Warning: One of the getParameter family of
methods called after reading from the ServletInputStream(), can't mix these
two! "
"<W> <ListenThread> Connection rejected: 'Login timed out after 5000 msec.
The socket came from [host=10.56.13.202,port=1539,localport=80] See property
weblogic.login.readTimeoutMillis to increase of decrease timeout. See
property weblogic.login.logReadTimeoutsProp to turn off these log
messages.'"
The editor says it comes from WL configuration
Please Help !
Christophe

hi.
I'm not clear on this - what do you mean you are running a J2EE application from
an editor?
Also the error is coming from a servlet. Is one of your servlets calling a
getParameter() method after reading from the ServletInputStream()? If it is it
should be corrected.
Regards,
Michael
Christophe Chastang wrote:
I'm running WL Express 5.1SP9 on a NT 4 server, Oracle 8.1.7 and an j2EE
application from an editor.
With the previous version of the application i wasn't having any problem,
since I installed the new version in the same environnement, I'm getting the
message when running the application :
"<E> <ServletContext-General> Warning: One of the getParameter family of
methods called after reading from the ServletInputStream(), can't mix these
two! "
"<W> <ListenThread> Connection rejected: 'Login timed out after 5000 msec.
The socket came from [host=10.56.13.202,port=1539,localport=80] See property
weblogic.login.readTimeoutMillis to increase of decrease timeout. See
property weblogic.login.logReadTimeoutsProp to turn off these log
messages.'"
The editor says it comes from WL configuration
Please Help !
Christophe--
Michael Young
Developer Relations Engineer
BEA Support

Message: "You have timed out from your previous session ..."

Hello, I’ve just installed Oracle Calendar Standalone 10.1.2. It’s working ok, but we get an annoying message every time we try to login, the message is: ”You have timed out from your previous session. Please sign in again.” When we try again it’s ok. So, our users have to put their user and password two times !
Any ideas ?

Hi, the problem seems related to the domain part of the URL. When the user puts http://machine:port he get the message, but when he write http://machine.our-domain.es all seems to be ok

Error "KSRPC.SendPacket: Timed out on Socket header" when stopping iAS

I am using iAS 6.5 on Win2k. I frequently get this error when stopping the app server:
KSRPC.SendPacket: Timed out on Socket header
Any ideas? Anything to worry about? Thanks.

I wouldn't worry about it if you only see the error when shutting down I also sometimes get the error. If you see the error when starting you could have problems as the kas would possibly not know some or all of the engines are running

Terminal.app Annoyance: Login timed out after 300 seconds

I have a default terminal "window group" of 4 Terminal windows. When I start Terminal.app it should provide 4 working terminal tabs, but frequently it happens that one or two sessions (tabs) fail to start and show the following message:
Login timed out after 300 seconds
[Process completed]

Post Unix and Terminal queries to the Unix forum under OS X Technologies.

"TNS-12535: TNS:operation timed out" error after listener restart

I have two related questions:
Scenario 1:
1. I have two remote Windows machines with database on each. One is Win 2003 Server (machine A) and another one is Win XP (machine B)
2. I can ping from A to B.
3. I can ping from B to A.
4. I can tnsping from A to B.
5. I CAN'T tnsping from B to A.
6. Windows Firewall on both machines are off.
What could be possible reason for point# 5?
Scenario 2:
Now, the second part:
1. I had an unwanted entry in tnsnames.ora on B which I removed.
2. Then I restarted the listener on B. Actually, I wanted to restart the one on A to check if that resolves issue mentioned in point# 5 above.
3. I tried tnsping from A to B but suprisingly it is also giving "operation timed out" error now. So now tnsping not working from either sides.
I didn't make any changes in listener.ora on B, just stopped it and started again. Only change made was removing unwanted entry in tnsnames.ora on B.
Why does that affected database connectivity from A to B which was working fine previously?
If any extra information needed please let me know, and thanks in advance for your answers.
- Ramesh

DB names on both machines: ORCL
listener.ora on B (Win XP) - This was working before listener restart, I mean, I was able to connect to DB on B from A.
# listener.ora Network Configuration File: C:\app\Test\product\11.2.0\dbhome_1\NETWORK\ADMIN\listener.ora
# Generated by Oracle configuration tools.
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = CLRExtProc)
(ORACLE_HOME = C:\app\Test\product\11.2.0\dbhome_1)
(PROGRAM = extproc)
(ENVS = "EXTPROC_DLLS=ONLY:C:\app\Test\product\11.2.0\dbhome_1\bin\oraclr11.dll")
(SID_DESC =
(GLOBAL_DBNAME = ORCL)
(ORACLE_HOME = c:\app\Test\product\11.2.0\dbhome_1)
(SID_NAME = ORCL)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = testpc)(PORT = 1521))
ADR_BASE_LISTENER = C:\app\Test
listener.ora on A (Win 2003 Server) - Never able to connect to DB on this machine from A.
# listener.ora Network Configuration File: D:\app\Administrator\product\11.2.0\dbhome_1\NETWORK\ADMIN\listener.ora
# Generated by Oracle configuration tools.
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = CLRExtProc)
(ORACLE_HOME = D:\app\Administrator\product\11.2.0\dbhome_1)
(PROGRAM = extproc)
(ENVS = "EXTPROC_DLLS=ONLY:D:\app\Administrator\product\11.2.0\dbhome_1\bin\oraclr11.dll")
(SID_DESC =
(GLOBAL_DBNAME = ORCL)
(ORACLE_HOME = D:\app\Administrator\product\11.2.0\dbhome_1)
(SID_NAME = ORCL)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = NRDBSVR.delldomain1.netreachasia.com)(PORT = 1521))
ADR_BASE_LISTENER = D:\app\Administrator
NOTE:
Machine A = NRDBSVR.delldomain1.netreachasia.com (Win 2003 Server)
Machine B = testpc (Win XP)

Message: "send mmap timed out" from a SSO instalation's HTTP_Server

Hi to everyone,
first of all my apologize if i have written this in a wrong forum but i did not find any forum in particular to SSO.
When looking at the error logs from Apache in a SSO installation (10.1.2.0.2) i have found these entries:
[Thu May 10 18:00:10 2012] [warn] [client 192.168.2.6] send mmap timed out
[Thu May 10 18:00:23 2012] [warn] [client 192.168.2.6] send mmap timed out
[Thu May 10 18:00:36 2012] [warn] [client 192.168.2.6] send mmap timed out
[Thu May 10 18:00:43 2012] [warn] [client 192.168.2.6] send mmap timed out
[Thu May 10 18:00:49 2012] [warn] [client 192.168.2.6] send mmap timed out
Does someone knows what they mean ??
Is this a critical error ??
what should i do to fix the problem ??
Thanks for your kind help
Regards
Carlos

I think you are confusing things here.
While you can change the port used for submission from your mail clients to your mail server, you cannot (should not) change the outgoing port for your smtp server. All mail servers expect incoming traffic on port 25, thus using port 587 will not get your mail delivered (it will go through your firewall, but that's about it).
If your mail server (not client) is behind a firewall with port 25 blocked, there is no way it can send mail to outside domains. So either get your ISP to let port 25 through for your server or use your ISP's smpt server to send mail (this can be done directly, or through your mail server relaying through your ISPs server).

IChat login/timing out. . . .Only on one account

Ok so i turn on my computer this morning and it times out when ever i try to login to aim using ichat. i though it might because i had i updated ichax last week so i uninstalled ichax and still it times out so then i signed using another aim account and it worked with no probelm. deleted all accounts and then tried my account info again but it still timed out. i also tried switching the ports
i am running 10.4.6
ichat v. 3.1.4
i looked at a bunch of threads involving ichat timing out but nothing seemed to anwser is prob thanks

Hi Rick,
I am aware that you are posting in serveral threads with an issue you have.
I am unable to gauge what the exact issue is with this fragmented approach.
Could you start your own thread and list what the problem is is as much detial as you have and what you have tried please
This item may help
http://discussions.apple.com/thread.jspa?threadID=527902
1:41 PM Wednesday; August 2, 2006

ORA-12535 TNS:operation timed out from SQLPlus and Enterprise Manager Conso

I keep getting a ORA-12535 TNS:operation timed out error, when I try to start my Database.
I know its a timeout error, but I would like to know what is timing out and why. All I want is the database its self to run to allow me to connect to it via SQLPlus and JDBC.
Is there any information on what the following services do and which ones I need to have running to use the database.
Oracle OLAP 9.0.101
Oracle OLAP Agent
Oracle oraHome90Agent
Oracle oraHome90ClientCache
Oracle OraHome90PagingServer
OracleOra90SNMPPeerEncapsulator
OracleOra90SNMPPeerMasterAgent
OracleOra90STNSListener
Thanks for any help Tony

Either reconfigure CONNECT_TIMEOUT to be 0, which means wait indefinitely, or reconfigure CONNECT_TIMEOUT to be some higher value. Or, if the timeout is unacceptably long, turn on tracing for further information.
If you have oracle metalink, then read the following note;
Note:119706.1 - Troubleshooting Guide TNS-12535 & ORA-12535 Errors

JDBC pooling Oracle driver Socket read timed out

I run Java EE application on Glassfish server v3 together with Oracle 12 DB on the same machine under Windows Server 2012 64bit. I use latest ojdbc7 driver.
Connection pool config:
<jdbc-connection-pool validation-table-name="DUAL" steady-pool-size="20" statement-cache-size="100" associate-with-thread="true" statement-timeout-in-seconds="30" idle-timeout-in-seconds="60" max-wait-time-in-millis="2000" validate-atmost-once-period-in-seconds="20" datasource-classname="oracle.jdbc.pool.OracleDataSource" pool-resize-quantity="5" max-pool-size="60" res-type="javax.sql.DataSource" name="dbPool" is-connection-validation-required="true">
<property name="driverClass" value="oracle.jdbc.OracleDriver"></property>
<property name="user" value="xxx"></property>
<property name="url" value="jdbc:oracle:thin:@(DESCRIPTION=(ENABLE=BROKEN)(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=127.0.0.1)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=orcl)))"></property>
<property name="password" value="xxx"></property>
<property name="portNumber" value="1521"></property>
<property name="databaseName" value="orcl"></property>
<property name="serverName" value="127.0.0.1"></property>
<property name="oracle.jdbc.ReadTimeout" value="300000"></property>
<property name="oracle.net.CONNECT_TIMEOUT" value="10000"></property>
</jdbc-connection-pool>
After 2 or 3 hours, when there is more than 1 user (3-5) using my application, it stops responding and I get this in glassfish logs
javax.enterprise.resource.resourceadapter.com.sun.enterprise.resource.allocator|_ThreadID=152;_ThreadName=Thread-2;|RAR5038:Unexpected exception while creating resource for pool dbPool. Exception : javax.resource.spi.ResourceAllocationException: Connection could not be allocated because: IO Error: Socket read timed out
Local Exception Stack:
Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.3.2.v20111125-r10461): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: Error in allocating a connection. Cause: Connection could not be allocated because: IO Error: Socket read timed out
From the database side it looks like this
Fatal NI connect error 12560, connecting to:
(LOCAL=NO)
VERSION INFORMATION:
TNS for 64-bit Windows: Version 12.1.0.1.0 - Production
Oracle Bequeath NT Protocol Adapter for 64-bit Windows: Version 12.1.0.1.0 - Production
Windows NT TCP/IP NT Protocol Adapter for 64-bit Windows: Version 12.1.0.1.0 - Production
Time: 13-JUN-2014 03:14:49
Tracing not turned on.
Tns error struct:
ns main err code: 12560
TNS-12560: TNS:protocol adapter error
ns secondary err code: 0
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
opiodr aborting process unknown ospid (3404) as a result of ORA-609
When I just reset db listener everything works ok for next 1-2 hours (depends on application load). So temporary solution is to run bat script from windows scheduler to reset the listener every 1h.
I tried everything I could find - applied these parameters:
- Sqlnet.ora:
SQLNET.INBOUND_CONNECT_TIMEOUT=180
SQLNET.EXPIRE_TIME=5
- Listener.ora:
INBOUND_CONNECT_TIMEOUT_LISTENER_IPC=120
But still without success

Is the problem here just that you need a connection pool that closes idle connections? Some pools will close idle connections after a time out period. And the pool lets you set that time out period. If the pool you are using doesn't provide that then use a different pool.

JRUN Apache connector not timing out despite setting recvTimeout

Hi,
 I have set a recvTimeout for the JRUN apache connector using the
[Thu Dec 15 15:29:48 2011] [notice] jrApache[3068: 20480] ap_escape_uri(TimeoutTest.cfm) = TimeoutTest.cfm
[Thu Dec 15 15:29:48 2011] [notice] jrApache[3068: 20480] jrun_trans: sub-request so DECLINED
[Thu Dec 15 15:29:48 2011] [notice] jrApache[3068: 20480] getRealPath(TimeoutTest.cfm) = TimeoutTest.cfm
[Thu Dec 15 15:29:48 2011] [notice] jrApache[3068: 20480] sent/avail/result 79/79/79
[Thu Dec 15 15:29:53 2011] [notice] jrApache[3068: 20480] read/len/total 4/4/4
[Thu Dec 15 15:29:53 2011] [notice] jrApache[3068: 20480] PROXY_GET_HEADER <- [11]
[Thu Dec 15 15:29:53 2011] [notice] jrApache[3068: 20480] read/len/total 4/4/4
[Thu Dec 15 15:29:53 2011] [notice] jrApache[3068: 20480] read/len/total 21/21/21
[Thu Dec 15 15:29:53 2011] [notice] jrApache[3068: 20480] HTTP_X_REQUESTED_WITH: <null>
[Thu Dec 15 15:29:53 2011] [notice] jrApache[3068: 20480] sent/avail/result 4/4/4
[Thu Dec 15 15:34:53 2011] [notice] jrApache[3068: 20480] 67.206.10.197:51050 jrConnect [9]
[Thu Dec 15 15:34:53 2011] [notice] jrApache[3068: 20480] sent/avail/result 4/4/4
[Thu Dec 15 15:34:53 2011] [notice] jrApache[3068: 20480] 67.206.10.197:51050 is reachable
[Thu Dec 15 15:34:53 2011] [notice] jrApache[3068: 20480] sent/avail/result 4/4/4
[Thu Dec 15 15:34:53 2011] [notice] jrApache[3068: 20480] 67.206.10.197:51050 is reachable
[Thu Dec 15 15:34:53 2011] [notice] jrApache[3068: 20480] 67.206.10.197:51050 returned socket [9] to pool
[Thu Dec 15 15:34:53 2011] [notice] jrApache[3068: 20480] jrRecv [11] timeout but server reachable so recv again
[Thu Dec 15 15:36:33 2011] [notice] jrApache[3068: 20480] read/len/total 4/4/4
[Thu Dec 15 15:36:33 2011] [notice] jrApache[3068: 20480] PROXY_GET_REALPATH <- [11]
[Thu Dec 15 15:36:33 2011] [notice] jrApache[3068: 20480] read/len/total 4/4/4
What does this error mean: jrRecv [11] timeout but server reachable so recv again
Is the jrun apache connector retrying or waiting some more for the page response ? I dont want it to retry / wait beyond the recvTimeout that I have set. What can I do in the config or elsewhere so that the recvTimeout returns as a timeout to apache and cleint without recv again attempt that it appears to be doing?
Thanks in advance for any help on this.
JRunConfig RecvTimeout 300
 I want this setting so long running pages will time out and return after 300 s with a timeout error and return the error back to the client.
However, I see that the timeout is not working and long running cfm pages continue to cycle without returning. Upon enabling the verbose option I see the following error logged for the long running page after the timeout occurs, but the page does not return anything and continues to wait on the client side.

sunilr1 wrote:
Hi,
 I have set a recvTimeout for the JRUN apache connector using the
JRunConfig RecvTimeout 300
 I want this setting so long running pages will time out and return after 300 s with a timeout error and return the error back to the client.
That is not the setting to time out long-running pages and then return a message. Why would you want to control request timeouts from JRun anyway? I don't think it's a good idea.
RecvTimeout determines how long to wait before timing out a socket receive call on a JRun server. The receive call is generally a synchronous call on a socket on a JRun server. It will throw an exception if the time out period is exceeded. In other words, a long-running page does not necessarily imply a long wait on a socket receive call.

Cisco CDN (Alarm 550001 (SEKeepalive) SE keepalive timed-out )

Dear Cisco Experts,
My systems as below:
CDSM, SR: version 3.2.1
SE1: version 3.2.1
SE2: version 2.6.3
Status (all devices): online (from CDSM: cms connectivity from all devices are OK)
SE1 can work normally, but SE2 doesn't work, Alarm:"SE SE2 keepalive timed-out" from CDSM.
log from SR:
192.168.11.0/24 20 SE2 (Down, Static)
192.168.8.0/24 20 SE1 (Operational, Static) (Load 1%, Device Threshold not reached)
0.0.0.0/0 10 SE1 (Operational, Static) (Load 1%, Device Threshold not reached)
0.0.0.0/0 10 SE2 (Down, Static)
I found infor from cisco about this alarm:
Alarm 550001 (SEKeepalive) SE keepalive timed-out or SE is not reachable.
Explanation Either the SR has not received keepalives from the SE, or the SE is not reachable.
Recommended Action Check the cables connected to the network device and the SE.
I'm sure about network connectivy is OK, problem should be from Version mismatch between SE and SR, Could you help me for this?
Many thanks and rgds.

Hi Long,
The alarm message that you are querying is indicating the keepalive between SR and SE has timed out.
There is UDP based keepalive messages sent from each SE to all SR periodically, by default it is 2 seconds. It is configurable via CDSM GUI. The destination port is 2323. This message has SE load information inside.
To check the keepalive message, you can execute following command on SR
SR# tcpdump udp port 2323
To debug keepalive, you can enable
SR#debug service-router keepalive
Then check service router errorlog under /local1
SR#type-tail errorlog/service_monitor_errorlog.current follow
check any error message popup. quit by Ctrl+C, then undebug all
SR#undebug all
Between 2.6.3 and 3.2.1, there is major difference in the format of packet. We do not recommend you to mix the version in production network. If you are requesting urgent assistance because of the service impact by this alarm, please do contact Cisco TAC support.
Best Regards,
Richard Xie

VPN is timing out

My VPN keeps timing out from my Windows and Mac machines. Windows OS is XP sp2 and Mac OS 10.4.
From XP the version is 5.0.x of the Cisco VPN software. I do not know what version I'm using from the Mac, but I use VPN on that one very infrequently so I couldn't say for sure I even have the problem on that machine.
Any ideas?

This document contains the most common solutions to IPsec VPN problems. These solutions come directly from service requests that the Cisco Technical Support have solved. Many of these solutions can be implemented prior to the in-depth troubleshooting of an IPsec VPN connection. As a result, this document is presented as a checklist of common procedures to try before you begin to troubleshoot a connection and call Cisco Technical Support.
http://www.cisco.com/en/US/products/ps6120/products_tech_note09186a00807e0aca.shtml

Tnsping timed out using dg4odbc from Oracle to MYSQL through ODBC

Hi,
I encountered problem when trying to connect from Oracle to MYSQL using dg4odbc, hope you can shed some light
Oracle database is 11.1.0.7 on SUSE Linux 64-bit.
Since the application which runs on MYSQL DB only offers ODBC driver on Windows platform, so I installed the 32-bit ODBC driver (from ServiceNow) on a 32-bit windows server (driver download from http://wiki.service-now.com/index.php?title=ODBC_Driver) .
created system DSN: MYSQLDEV, The DSN connection works fine. I then installed Oracle 11.2.0.1 gateway for ODBC 32-bit on the same windows server, the following configurations were done:
On 32-bit Windows server:
in gatewayHome\hs\admin
initMYSQLDEV.ora:
# HS init parameters
HS_FDS_CONNECT_INFO = MYSQLDEV
HS_FDS_TRACE_LEVEL = DEBUG
in gatewayHome\network\admin:
listener.ora
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = abcdes.sda.sdva.com)(PORT = 1521))
SID_LIST_LISTENER=
(SID_LIST=
(SID_DESC=
(SID_NAME=MYSQLDEV)
(ORACLE_HOME=C:\product\11.2.0\tg_1)
(PROGRAM=dg4odbc)
ADR_BASE_LISTENER = C:\product\11.2.0\tg_1
stop and started listener on windows server and check listener status
C:\product\11.2.0\tg_1\bin>lsnrctl status listener
LSNRCTL for 32-bit Windows: Version 11.2.0.1.0 - Production on 29-MAR-2012 21:42:08
Copyright (c) 1991, 2010, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=abcdes.sda.sdva.com)(PORT=1521)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for 32-bit Windows: Version 11.2.0.1.0 - Produ
ction
Start Date 29-MAR-2012 21:11:36
Uptime 0 days 0 hr. 30 min. 32 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File C:\product\11.2.0\tg_1\network\admin\listener.ora
Listener Log File c:\product\11.2.0\tg_1\diag\tnslsnr\abcdes\list
ener\alert\log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=abcdes.sda.sdva.com)(PORT=1521)))
Services Summary...
Service "MYSQLDEV" has 1 instance(s).
Instance "MYSQLDEV", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
On Linux server where Oracle DB resides.
Added the following tns entry "jelly" on the Linux server ORACLE_HOME/network/admin:
jelly =
(DESCRIPTION=
(ADDRESS=(PROTOCOL=TCP)
(HOST=abcdes.sda.sdva.com)
(PORT=1521))
(CONNECT_DATA=(SID=MYSQLDEV))(HS=OK)
tnsping from Linux server (64-bit) failed with timeout error:
tnsping jelly
TNS Ping Utility for Linux: Version 11.1.0.7.0 - Production on 29-MAR-2012 21:12:38
Copyright (c) 1997, 2008, Oracle. All rights reserved.
Used parameter files:
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION= (ADDRESS=(PROTOCOL=TCP) (HOST=abcdes.sda.sdva.com) (PORT=1521)) (CONNECT_DATA=(SID=MYSQLDEV))(HS=OK))
TNS-12535: TNS:operation timed out
tnsping from Windows server works fine: (added same tnsnames entry on windows server for testing purpose only)
C:\product\11.2.0\tg_1\bin>tnsping jelly
TNS Ping Utility for 32-bit Windows: Version 11.2.0.1.0 - Production on 29-MAR-2
012 21:45:20
Copyright (c) 1997, 2010, Oracle. All rights reserved.
Used parameter files:
C:\product\11.2.0\tg_1\network\admin\sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=abcdes.sda.sdva.com)(PORT=1521)) (CONNECT_DATA=(SID=MYSQLDEV)) (HS=OK))
OK (20 msec)
if listener is not listening to the service, then the tnsping on the windows server should fail as well.
I don't know why only the tnsping from Linux failed, is it due to the 32-bit ODBC uncompatibility with 64-bit oracle server? or my configuration problem?
Of course, when I created the DB link from oracle, the connection failed with
create database link mysqldev connect to xxxx identified by "xxxxx" using 'jelly';
Database link created.
select * from tab1;
ERROR at line 1:
ORA-28545: error diagnosed by Net8 when connecting to an agent
Unable to retrieve text of NETWORK/NCR message 65535
ORA-02063: preceding 2 lines from MYSQLDEV
Thanks for your help,

Hi Mike,
This is part of the tnsping.trc file which contains the error. IP address is in the tnsnames entry with this tnsping.
nsopen: opening transport...
nttcon: entry
nttcon: toc = 1
nttcnp: entry
nttcnp: creating a socket.
nttcnp: exit
nttcni: entry
nttcni: Tcp conn timeout = 0 (ms)
nttcni: trying to connect to socket 5.
ntt2err: entry
ntt2err: soc 5 error - operation=1, ntresnt[0]=505, ntresnt[1]=110, ntresnt[2]=0
ntt2err: exit
nttcni: exit
nttcon: exit
nserror: entry
nserror: nsres: id=0, op=65, ns=12535, ns2=12560; nt[0]=505, nt[1]=110, nt[2]=0; ora[0]=0, ora[1]=0, ora[2]=0
nsopen: unable to open transport
nsiocancel: entry
nsiofrrg: entry
nsiofrrg: cur = 53b9f8
nsbfr: entry
nsbaddfl: entry
nsbaddfl: normal exit
nsbfr: normal exit
nsiofrrg: exit
nsiocancel: exit
nsvntx_dei: entry
nsvntx_dei: exit
nsopenfree_nsntx: nlhthdel from mplx_ht_nsgbu, ctx=53a7e0 nsntx=53ade0
nsiocancel: entry
nsiofrrg: entry
nsiofrrg: exit
nsiocancel: exit
nsmfr: entry
nsmfr: 2712 bytes at 0x53ade0
nsmfr: normal exit
nsmfr: entry
nsmfr: 1528 bytes at 0x53a7e0
nsmfr: normal exit
nsopen: error exit
nscall: error exit
nscall: entry
nscall: connecting...
nsclose: entry
nsclose: normal exit
nladget: entry
nladget: exit
nsmfr: entry
nsmfr: 264 bytes at 0x528900
nsmfr: normal exit
nladtrm: entry
nladtrm: exit
nscall: error exit
nlse_term_audit: entry
nlse_term_audit: exit
Thanks,

Login timed out from Socket Listener?

Similar Messages

Maybe you are looking for