This bug happens when multiple requests for a session come in before
the first request completes (Ajax on the page can cause this) and
the first request calls terminate() on the session (e.g. from a log
out link or in response to an exception during request processing).
The session terminates properly, but the threads for the other
queued requests for the now terminated sessions are stuck. This
prevents the app from restarting under wotaskd control (other than
force quitting it). An example trace from one such stuck thread
(highly mutilated, not my fault):
Are you kidding me? How has this one survived this long? Why doesn't
terminate check in the session? Won't a terminated session .notify()
the TimoutEntry?? That's asinine. This is cruising for a Wonder fix,
I think.
ms
_______________________________________________
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]
