IZ95787: ILLEGALMONITORSTATEEXCEPTION IN LDAP CONNECTION.CLEANUP()

APAR status

• Closed as program error.

Error description

• Error Message: java.lang.IllegalMonitorStateException
  .
  Stack Trace: at
  com.sun.jndi.ldap.Connection.cleanup(Connection.java:685)
  at com.sun.jndi.ldap.Connection.run(Connection.java:992)
  at java.lang.Thread.run(Thread.java:811)
  
  Another stack trace:
  
  Caused by: java.lang.IllegalMonitorStateException
  at com.sun.jndi.ldap.Connection.cleanup(Connection.java:685)
  at
  com.sun.jndi.ldap.Connection.writeRequest(Connection.java:431)
  at com.sun.jndi.ldap.LdapClient.ldapBind(LdapClient.java:366)
  Page 79 of 98
  at
  com.sun.jndi.ldap.LdapClient.authenticate(LdapClient.java:224)
  at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2697)
  at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:316)
  

Local fix

Problem summary

• When LDAP client receives connection reset from the LDAP server,
  the connection object does a cleanup. During the cleanup, all
  the pending LDAP requests needs to be notified to do the cleanup
  immediately. The "IllegalMonitorStateException" occurs when
  the LdapRequest object is notified without synchronizing it.
  

Problem conclusion

• This defect will be fixed in:
  5.0.0 SR12FP5
  .
  The JDK has been updated to synchronize the LdapRequest object
  while notifying the pending LdapRequests during the connection
  cleanup.
  .
  To obtain the fix:
  Install build 20110317 or later
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  JAVA 5 CLASS LI

• Fixed component ID

  620500130

Applicable component levels

• R500 PSN

     UP