JDK-6748156 : add an new JNDI property to control the boolean flag WaitForReply (JDK5)
  • Type: Enhancement
  • Component: core-libs
  • Sub-Component: javax.naming
  • Affected Version: 5.0,5.0u11
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: linux_suse_sles_10
  • CPU: x86
  • Submitted: 2008-09-13
  • Updated: 2017-05-16
  • Resolved: 2009-05-18
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other Other Other JDK 6 JDK 7
5.0u19-rev b03Fixed 5.0u20-revFixed 5.0u21Fixed 6u14Fixed 7Fixed
Related Reports
Duplicate :  
Relates :  
Relates :  
cannot cancel LDAP search operation via JNDI before the LDAP server sends the first batch of answers

The problem can be solved when changing the class com.sun.jndi.ldap.LdapCtx, method c_search(Name name, String filter, SearchControls cons, Continuation cont), row 1747. This method invokes "searchAux" with a parameter called "WaitForReply". In the original code "waitForReply" is set to true. A JNDI property is in order to allow customer to change "WaitForReply" to false in their code.

EVALUATION The LDAP service provider implementation normally waits until the first reply from the server is received. The customer would like to be able to abandon a long-running search operation without having to wait for the first reply. A new boolean-valued JNDI property could be used to override the default behaviour. *** (#1 of 1): [ UNSAVED ] ###@###.###

SUGGESTED FIX Introduce a new string-valued boolean property: com.sun.jndi.ldap.search.waitForReply Its values are "true" (default) and "false" and it is only examined when an LDAP context is created.