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 Availability Release.
To download the current JDK release, click here.
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 |
|---|---|---|
6u33 b33Fixed  |
7u40Fixed |
8Fixed |
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
|