On Dec 1, 2008, at 3:38 PM, Andrew Lindesay wrote:
Hello Mike;
I guess that's only really possible through a slip-up in the top-
level exception handling... hmmm... thanks.
Or sleep() or terminate() not calling super or throwing an exception.
Or two requests for a session coming very close together and the first
calling terminate() on the session (e.g. double clicking a Logout link
or Ajax fun).
Chuck
cheers.
Does anybody know what the monitor object for this synchronised-
block might be for?
[1] java.lang.Object.wait (native method)
[2] java.lang.Object.wait (Object.java:474)
[3] com.webobjects.appserver.WOSessionStore.checkOutSessionWithID
(WOSessionStore.java:191)
It means a session didn't get checked back in properly at some
point ... The monitor is blocking on the TimeoutEntry to see if the
session has timed out, but checking out a session increments a
counter on that, so it basically waits until the counter goes back
down to zero before it can claim the session.
___
Andrew Lindesay
www.lindesay.co.nz
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/chill%40global-village.net
This email sent to [EMAIL PROTECTED]
--
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 protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
