On Jan 28, 2009, at 11:10, Stamenkovic Florijan wrote:
Also, when I look at the source of ReentrantLock, I see that this
exception is thrown because of:
if (Thread.currentThread() != owner)
throw new IllegalMonitorStateException();
So, the thread trying to unlock does not actually own the lock, the
other thread owns it. AFAIK the only way to make this happen is
calling unlock, without the same thread obtaining a lock before
that. Which is most definitively a bug. Or do I see this wrong?
Or calling unlock() more times then lock() was called....
F
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
