aspose file tools*
The moose likes EJB and other Java EE Technologies and the fly likes WebSphere 4.0.x and JNDI Timeout Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Java 8 in Action this week in the Java 8 forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "WebSphere 4.0.x and JNDI Timeout" Watch "WebSphere 4.0.x and JNDI Timeout" New topic
Author

WebSphere 4.0.x and JNDI Timeout

Shoua heu
Greenhorn

Joined: Feb 16, 2004
Posts: 2
This has probably been asked already, but does anyone have updated information on how to increase timeout when doing JNDI calls with WebSphere 4.0.x? I've read that Sun JDK 1.4 and later have environment properties to address JNDI timeout (DNS and LDAP), but since WebSphere v4 and v5 are based on JDK 1.3.1 this doesn't work.
Is there any IBM WebSphere specific coding that I can do to resolve timeout exception like this one:
----- Begin backtrace for rootCause
java.net.ConnectException: Operation timed out: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:345)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:157)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:144)
at java.net.Socket.<init>(Socket.java:294)
at java.net.Socket.<init>(Socket.java:121)
at com.sun.jndi.ldap.Connection.<init>(Connection.java:215)
at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.java:127)
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2398)
at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:258)
at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:91)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:674)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:255)
at javax.naming.InitialContext.init(InitialContext.java:231)
at javax.naming.InitialContext.<init>(InitialContext.java:207)
at javax.naming.directory.InitialDirContext.<init>(InitialDirContext.java:92)
This appears to occur sometimes when I am creating the context and others when I am doing LDAP queries.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: WebSphere 4.0.x and JNDI Timeout
 
Similar Threads
LDAP server Access Error in java
Unable to create a JNDI InitialContext problem
help jboss
cannot connect to LDAP through JNDI
Attemplting to connect to a public LDAP directory