JDK-8042857 : 14 stuck threads waiting for notification on LDAPRequest
  • Type: Bug
  • Component: core-libs
  • Sub-Component: javax.naming
  • Affected Version: 6
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2014-05-09
  • Updated: 2015-01-21
  • Resolved: 2014-05-23
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.
JDK 6 JDK 7 JDK 8 JDK 9
6u85Fixed 7u72Fixed 8u20Fixed 9 b15Fixed
Related Reports
Relates :  
Description
When a default read timeout is not provided and the host cannot be contacted, com.sun.jndi.ldap.Connection.readReply() will get stuck in an infinite loop.
Comments
This fix has been undone as it was a violation of the spec. See JDK-8065238.
2015-01-21

Seems this is not a stopper for CPU14_03. The fix requires jdk6 u81 build. Would like to avoid one more jdk6 CPU14_03 for this only fix.
2014-06-04