Loading...

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: P2
Fix Version/s: 6u33
Affects Version/s: 6
Component/s: core-libs
Labels:

Subcomponent:
javax.naming
Resolved In Build:
b33
CPU:

generic
OS:

generic

Issue	Fix Version	Assignee	Priority	Status	Resolution	Resolved In Build
JDK-2225544	8	Robert Mckenna	P2	Closed	Fixed	b47
JDK-8018867	7u45	Robert Mckenna	P2	Closed	Fixed	b01
JDK-2225543	7u40	Robert Mckenna	P2	Closed	Fixed	b01
JDK-8000727	6u38	Robert Mckenna	P2	Closed	Fixed	b01
JDK-8000726	6u37	Robert Mckenna	P2	Resolved	Fixed	b31
JDK-2229346	6u35	Robert Mckenna	P2	Resolved	Fixed	b31
JDK-2227178	6u34	Robert Mckenna	P2	Resolved	Fixed	b31

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

backported by

JDK-2227178 Deadlock in jndi ldap connection cleanup

Resolved

JDK-2229346 Deadlock in jndi ldap connection cleanup

Resolved

JDK-8000726 Deadlock in jndi ldap connection cleanup

Resolved

JDK-2225543 Deadlock in jndi ldap connection cleanup

Closed

JDK-2225544 Deadlock in jndi ldap connection cleanup

Closed

JDK-8000727 Deadlock in jndi ldap connection cleanup

Closed

JDK-8018867 Deadlock in jndi ldap connection cleanup

Closed

(2 backported by)

Assignee:: Robert Mckenna

Reporter:: Shadow Bug

Votes:: 0 Vote for this issue

Watchers:: 6 Start watching this issue

Created:: 2012-06-06 14:40

Updated:: 2014-11-19 11:08

Resolved:: 2012-06-29 15:12

Imported:: 17/Sep/12 11:55 PM

Indexed:: 05/Sep/12 3:46 AM

Details

Backports

Description

Attachments

Issue Links

Activity

People

Dates