Re: Where is the deadlock culprit?
Re: Where is the deadlock culprit?
- Subject: Re: Where is the deadlock culprit?
- From: Chuck Hill <email@hidden>
- Date: Wed, 3 Dec 2008 11:28:26 -0800
On Dec 3, 2008, at 11:12 AM, Anjo Krank wrote:
Am 03.12.2008 um 19:33 schrieb Kieran Kelleher:
- java.lang.Object.wait(long) @bci=0 (Compiled frame; information
may be imprecise)
- java.lang.Object.wait() @bci=2, line=474 (Compiled frame)
- com.webobjects.eocontrol.EOEditingContext.lock() @bci=28,
line=4685 (Compiled frame)
- er.extensions.eof.ERXEC.lock() @bci=353, line=480 (Compiled frame)
- wk.eofextensions.MultiECLockManager.lock() @bci=38, line=69
(Compiled frame)
- wk.webobjects.appserver.WKSession.awake() @bci=8, line=52
(Interpreted frame)
An EC hasn't been unlocked and you're not using auto-unlocking.
Worse! He is using MultiECLockManager AND ERXEC! That looks like a
recipe for disaster to me. I'd guess some interaction between the
two, or some uncaught exception is skipping the unlock of the default
EC.
Chuck
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden