Re: Where is the deadlock culprit?
Re: Where is the deadlock culprit?
- Subject: Re: Where is the deadlock culprit?
- From: Guido Neitzer <email@hidden>
- Date: Wed, 3 Dec 2008 11:56:32 -0700
Probably:
-
com
.webobjects
.appserver.WOSessionStore.checkOutSessionWithID(java.lang.String,
com.webobjects.appserver.WORequest) @bci=48, line=207 (Interpreted
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)
- wk.cheetah.Session.awake() @bci=1, line=467 (Interpreted frame)
-
com
.webobjects
.appserver
.WOSession._awakeInContext(com.webobjects.appserver.WOContext)
@bci=61, line=720 (Interpreted frame)
Are you maybe not catching exceptions in sleep() or terminate() on the
session (and direct action) properly?
cug
_______________________________________________
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