It's not a secret anymore!
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
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

WebSphere 4.0.x and JNDI Timeout

Shoua heu

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 Operation timed out: connect
at Method)
at com.sun.jndi.ldap.Connection.<init>(
at com.sun.jndi.ldap.LdapClient.<init>(
at com.sun.jndi.ldap.LdapCtx.connect(
at com.sun.jndi.ldap.LdapCtx.<init>(
at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(
at javax.naming.spi.NamingManager.getInitialContext(
at javax.naming.InitialContext.getDefaultInitCtx(
at javax.naming.InitialContext.init(
at javax.naming.InitialContext.<init>(
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:
subject: WebSphere 4.0.x and JNDI Timeout
It's not a secret anymore!