JDK-7174887 : Deadlock in jndi ldap connection cleanup
  • Type: Bug
  • Component: core-libs
  • Sub-Component: javax.naming
  • Affected Version: 6
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2012-06-06
  • Updated: 2014-11-19
  • Resolved: 2012-06-29
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 Availabitlity Release.

To download the current JDK release, click here.
JDK 6 JDK 7 JDK 8
6u33 b33Fixed 7u40Resolved 8Resolved
Description
SHORT SUMMARY: Deadlock in jndi/ldap connection cleanup
INDICATORS: Attached stacktrace
COUNTER INDICATORS: No deadlock
TRIGGERS: Seemingly when the poolcleaner run and a connection cleanup occur 
at the same time.
KNOWN WORKAROUND: na
PRESENT SINCE: na
HOW TO VERIFY: Very tricky to reproduce
NOTES FOR SE:
REGRESSION: unknown

Comments
EVALUATION http://hg.openjdk.java.net/hsx/hotspot-comp/jdk/rev/ecc5dd3790a1
2012-08-14

EVALUATION no need for processConnectionClosure to run within the sync block around Connections.
2012-06-28