Re: WOSessionStore deadlock
Re: WOSessionStore deadlock
- Subject: Re: WOSessionStore deadlock
- From: Guido Neitzer <email@hidden>
- Date: Wed, 29 Apr 2009 10:05:35 -0700
On Apr 29, 2009, at 9:58 AM, Chuck Hill wrote:
I have 3 threads like this, all waiting on the same monitor:
"WorkerThread15" prio=5 tid=0x08995400 nid=0x8995600 in
Object.wait() [0xbf0dd000..0xbf0ddb80]
at java.lang.Object.wait(Native Method)
- waiting on <0x34000548> (a
com.webobjects.appserver.WOSessionStore$TimeoutEntry)
at java.lang.Object.wait(Object.java:474)
at
com
.webobjects
.appserver.WOSessionStore.checkOutSessionWithID(WOSessionStore.java:
207)
- locked <0x34000548> (a com.webobjects.appserver.WOSessionStore
$TimeoutEntry)
at
com
.webobjects
.appserver.WOApplication.restoreSessionWithID(WOApplication.java:
1546)
at
er
.extensions
.appserver.ERXApplication.restoreSessionWithID(ERXApplication.java:
2028)
...
I noticed Wonder has something to detect session store deadlocks,
but it works only when concurrent requests are off, and we have
that feature turned on.
What can be causing a session to be checked out, but not checked in
again?
Bad coding? :-P
I can think of only four causes:
1. Exception thrown from sleep().
2. Exception thrown from terminate() (not 100% sure of that)
3. Exception thrown from WODirectAction.performAction() (though I
am pretty sure this was fixed in WO 5.3)
It wasn't. At least not for everything.
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