Looks like a stupid bug in the octetstring...Logger

Question

Hi all,
My WLS hanged on no disk space left and most threads were hanging as follows:
"ExecuteThread: '8' for queue: 'default'" daemon prio=5 tid=0x5f4c0d80 nid=0x6a0
waiting on monitor [0x602af000..0x602afdb8]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at com.octetstring.vde.util.Logger.writeLock(Logger.java:195)
at com.octetstring.vde.util.Logger.alog(Logger.java:310)
at com.octetstring.vde.MessageHandler.doSearch(MessageHandler.java:312)
at com.octetstring.vde.MessageHandler.answerRequest(MessageHandler.java:67)
at com.octetstring.vde.WorkThread.executeWorkQueueItem(WorkThread.java:82)
at weblogic.ldap.LDAPExecuteRequest.execute(LDAPExecuteRequest.java:28)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
I noted that there was no other thread inside the
at com.octetstring.vde.util.Logger.alog(Logger.java:310)
that were NOT in the
at com.octetstring.vde.util.Logger.writeLock(Logger.java:195)
This makes me think that the 'Logger.alog()' method looks like this:
wrtiteLock();
writeToDisk(data); // whatever
writeUnLock();
instead of:
writeLock();
try{
writeToDisk(data); // whatever
finally {
writeUnLock();
Send it to the developers please, will you?
Thanks,
Mike.

Answer 1

and a valuable lesson: whenever you think you've found a bug in one of the core classes, always consider that if it really were a bug minds immeasurably superior to yours would have found and reported it a long time ago.
Ergo, whenever you find what you think is a bug in the core classes you should change your thinking to "what have I done wrong" rather than "there's a bug in Java".
my sincere apologies to Orson Wells.