-
Bug
-
Resolution: Fixed
-
P4
-
6
-
None
-
b130
-
generic
-
generic
-
Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2208822 | 6u27 | Robert Mckenna | P2 | Closed | Fixed | b01 |
| JDK-2208674 | 6u26-rev | Robert Mckenna | P2 | Resolved | Fixed | b21 |
| JDK-2208651 | 6u25-rev | Robert Mckenna | P2 | Resolved | Fixed | b21 |
| JDK-2206341 | 6u24-rev | Robert Mckenna | P2 | Closed | Fixed | b25 |
The LDAP request queue is normally flushed when cleaning up during a socket connection
shutdown. In multi-threaded JNDI/LDAP applications an IllegalMonitorStateException can
sometimes be thrown when flushing this queue:
java.lang.IllegalMonitorStateException
at java.lang.Object.notify(Native Method)
at com.sun.jndi.ldap.Connection.cleanup(Connection.java:663)
at com.sun.jndi.ldap.Connection.run(Connection.java:965)
at java.lang.Thread.run(Thread.java:732)
shutdown. In multi-threaded JNDI/LDAP applications an IllegalMonitorStateException can
sometimes be thrown when flushing this queue:
java.lang.IllegalMonitorStateException
at java.lang.Object.notify(Native Method)
at com.sun.jndi.ldap.Connection.cleanup(Connection.java:663)
at com.sun.jndi.ldap.Connection.run(Connection.java:965)
at java.lang.Thread.run(Thread.java:732)
- backported by
-
JDK-2208651 Need synchronized access when flushing the LDAP request queue
-
- Resolved
-
-
-
- Resolved
-
-
-
- Closed
-
-
-
- Closed
-