-
Bug
-
Resolution: Fixed
-
P3
-
7u72
-
b83
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8142068 | emb-9 | Robert Mckenna | P3 | Resolved | Fixed | team |
JDK-8140914 | 8u91 | Robert Mckenna | P3 | Resolved | Fixed | b01 |
JDK-8136853 | 8u72 | Robert Mckenna | P3 | Resolved | Fixed | b01 |
JDK-8147246 | emb-8u91 | Robert Mckenna | P3 | Resolved | Fixed | b01 |
JDK-8136857 | 7u95 | Robert Mckenna | P3 | Closed | Fixed | b02 |
JDK-8136862 | 6u111 | Robert Mckenna | P3 | Resolved | Fixed | b02 |
Deadlock in LDAP code.
.
Found one Java-level deadlock:
=============================
"Thread-1926":
waiting to lock monitor 0x0000000001988f50 (object 0xfffffd7fe3946018, a
com.sun.jndi.ldap.EventSupport),
which is held by "<ThreadName>"
"LdapDatafillUpdateTimer":
waiting to lock monitor 0x0000000001021760 (object 0xfffffd7fe39463f8, a
java.util.Vector),
which is held by "Thread-1926"
.
Java stack information for the threads listed above:
===================================================
"Thread-1926":
at com.sun.jndi.ldap.LdapCtx.fireUnsolicited(LdapCtx.java:3529)
- waiting to lock <0xfffffd7fe3946018> (a
com.sun.jndi.ldap.EventSupport)
at
com.sun.jndi.ldap.LdapClient.notifyUnsolicited(LdapClient.java:1574)
at
com.sun.jndi.ldap.LdapClient.processConnectionClosure(LdapClient.java:504)
- locked <0xfffffd7fe39463f8> (a java.util.Vector)
at com.sun.jndi.ldap.Connection.cleanup(Connection.java:693)
at com.sun.jndi.ldap.Connection.run(Connection.java:992)
at java.lang.Thread.run(Thread.java:745)
"<ThreadName>":
at
com.sun.jndi.ldap.LdapClient.removeUnsolicited(LdapClient.java:1498)
- waiting to lock <0xfffffd7fe39463f8> (a java.util.Vector)
at com.sun.jndi.ldap.LdapCtx.removeUnsolicited(LdapCtx.java:3513)
- locked <0xfffffd7fe3946018> (a com.sun.jndi.ldap.EventSupport)
at com.sun.jndi.ldap.LdapCtx.close(LdapCtx.java:2581)
- locked <0xfffffd7fe3945eb0> (a com.sun.jndi.ldap.LdapCtx)
at xxx.closeEventContext(LdapContextManager.java:49)
... removed...
.
Found one Java-level deadlock:
=============================
"Thread-1926":
waiting to lock monitor 0x0000000001988f50 (object 0xfffffd7fe3946018, a
com.sun.jndi.ldap.EventSupport),
which is held by "<ThreadName>"
"LdapDatafillUpdateTimer":
waiting to lock monitor 0x0000000001021760 (object 0xfffffd7fe39463f8, a
java.util.Vector),
which is held by "Thread-1926"
.
Java stack information for the threads listed above:
===================================================
"Thread-1926":
at com.sun.jndi.ldap.LdapCtx.fireUnsolicited(LdapCtx.java:3529)
- waiting to lock <0xfffffd7fe3946018> (a
com.sun.jndi.ldap.EventSupport)
at
com.sun.jndi.ldap.LdapClient.notifyUnsolicited(LdapClient.java:1574)
at
com.sun.jndi.ldap.LdapClient.processConnectionClosure(LdapClient.java:504)
- locked <0xfffffd7fe39463f8> (a java.util.Vector)
at com.sun.jndi.ldap.Connection.cleanup(Connection.java:693)
at com.sun.jndi.ldap.Connection.run(Connection.java:992)
at java.lang.Thread.run(Thread.java:745)
"<ThreadName>":
at
com.sun.jndi.ldap.LdapClient.removeUnsolicited(LdapClient.java:1498)
- waiting to lock <0xfffffd7fe39463f8> (a java.util.Vector)
at com.sun.jndi.ldap.LdapCtx.removeUnsolicited(LdapCtx.java:3513)
- locked <0xfffffd7fe3946018> (a com.sun.jndi.ldap.EventSupport)
at com.sun.jndi.ldap.LdapCtx.close(LdapCtx.java:2581)
- locked <0xfffffd7fe3945eb0> (a com.sun.jndi.ldap.LdapCtx)
at xxx.closeEventContext(LdapContextManager.java:49)
... removed...
- backported by
-
JDK-8136853 Deadlock in JNDI LDAP implementation when closing the LDAP context
-
- Resolved
-
-
JDK-8136862 Deadlock in JNDI LDAP implementation when closing the LDAP context
-
- Resolved
-
-
JDK-8140914 Deadlock in JNDI LDAP implementation when closing the LDAP context
-
- Resolved
-
-
JDK-8142068 Deadlock in JNDI LDAP implementation when closing the LDAP context
-
- Resolved
-
-
JDK-8147246 Deadlock in JNDI LDAP implementation when closing the LDAP context
-
- Resolved
-
-
JDK-8136857 Deadlock in JNDI LDAP implementation when closing the LDAP context
-
- Closed
-
(1 backported by)