Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: Where is the deadlock culprit?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Where is the deadlock culprit?

Subject: Re: Where is the deadlock culprit?
From: Anjo Krank <email@hidden>
Date: Wed, 3 Dec 2008 20:12:32 +0100


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.

Cheers, Anjo
_______________________________________________
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


Follow-Ups:

Re: Where is the deadlock culprit?
From: Chuck Hill <email@hidden>


References:  
  >Where is the deadlock culprit? (From: Kieran Kelleher <email@hidden>)




Prev by Date:
Re: Wonder prototypes docs ?

Next by Date:
Re: Where is the deadlock culprit?

Previous by thread:
Re: Where is the deadlock culprit?

Next by thread:
Re: Where is the deadlock culprit?

Index(es):

Date
Thread