Re: Application Stops Responding - Strange Conditions
Re: Application Stops Responding - Strange Conditions
- Subject: Re: Application Stops Responding - Strange Conditions
- From: Hunter Hillegas <email@hidden>
- Date: Wed, 20 Apr 2005 08:54:59 -0700
Anjo,
Using the deadlock detection backs up what the thread dump says.
There is an error in the session check-out: old context: contextId: 5
request
...
java.lang.IllegalStateException: Context with id '4' did check out again
So, I assume this means that that context 4 tried to check out a
session that context 5 already had checked out?
Am I reading this correctly?
I wonder why the hell this happens with direct actions and not
component actions...
Hunter
On Apr 20, 2005, at 1:18 AM, Anjo Krank wrote:
Other than that, look in ERXApp's code to find out about the
session store deadlock detection, it might give you some hints (you
need to run single-threaded to use it).
_______________________________________________
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