-
Type:
Enhancement
-
Resolution: Won't Fix
-
Priority:
P5
-
None
-
Affects Version/s: 5.0
-
Component/s: core-libs
-
x86
-
windows_xp
A DESCRIPTION OF THE REQUEST :
With Java 6, the property com.sun.jndi.ldap.read.timeout can be specified in order to allow ldap operations to timeout when using the JNDI context factory com.sun.jndi.ldap.LdapCtxFactory. Providing similar support within Java 5 is desirable as an unresponsive LDAP instance can halt a varierty of application components that perform JNDI lookups.
JUSTIFICATION :
Allow failover to other LDAP URLS that can be specified in a PROVIDER_URL list.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
If a read timeout occurs, LdapCtxFactory operations would return a NamingException with the error message "LDAP response read timed out".
ACTUAL -
Use of any JNDI based LDAP operation supported by com.sun.jndi.ldap.LdapCtxFactory will never return should the LDAP instance become unresponsive.
CUSTOMER SUBMITTED WORKAROUND :
Restart application after editting the LDAP URL to remove any unresponsive LDAP instance.
With Java 6, the property com.sun.jndi.ldap.read.timeout can be specified in order to allow ldap operations to timeout when using the JNDI context factory com.sun.jndi.ldap.LdapCtxFactory. Providing similar support within Java 5 is desirable as an unresponsive LDAP instance can halt a varierty of application components that perform JNDI lookups.
JUSTIFICATION :
Allow failover to other LDAP URLS that can be specified in a PROVIDER_URL list.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
If a read timeout occurs, LdapCtxFactory operations would return a NamingException with the error message "LDAP response read timed out".
ACTUAL -
Use of any JNDI based LDAP operation supported by com.sun.jndi.ldap.LdapCtxFactory will never return should the LDAP instance become unresponsive.
CUSTOMER SUBMITTED WORKAROUND :
Restart application after editting the LDAP URL to remove any unresponsive LDAP instance.