• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

WebSphere 4.0.x and JNDI Timeout

 
Shoua heu
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic