Use jstack to see the stack traces of the deadlocked request threads. Also Wonder has a SessionDeadlock detection feature that is useful to trap session deadlocks, report them and fix them. I have found that to be the most useful way to find bugs that cause sesion deadlocks. In my case, and this was a long time ago so the details are hazy, Session deadlocks were being caused by an error in appendToResponse of the ExcelGenerator wrapper because the Wonder install had "merged" with old versiona and I had two versions of the same POI jar in the deployed framework.
HTH, Kieran On Mar 9, 2010, at 9:40 PM, Paul Hoadley wrote: > On 10/03/2010, at 1:04 PM, Chuck Hill wrote: > >> Did the app actually stop and restart the previous night? If you have a >> stuck session, it will start refusing sessions, but it can't actually stop >> and restart. That sounds like what you are seeing. > > Ah, bingo. It didn't stop and restart. > > JavaMonitor is telling me there are 13 active sessions, and I can guarantee > that there are not 13 users currently logged in. Where do I start looking to > debug these stuck sessions? > > > -- > Paul. > > http://logicsquad.net/ > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-deploy mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/webobjects-deploy/kieran_lists%40mac.com > > This email sent to [email protected] _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-deploy mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com This email sent to [email protected]
