kill -s 3 <java pid> will cause Java to dump all of its threads and locks to the console. Tomcat will also log the dump to catalina.out. This means you can just paste the dump to an email, rather than screenshots.
Regards, Steve
Shash Chatterjee wrote:
Phil,
Now that I am lookingfor it, I was able to see the hang with the nojms-cocoon + struts webapp.
Attached are the stack (two screenshots, scrolled), threads and monitors view from Eclipse.
Shash
Steve & Phil,
I was able to reproduce the thread problem, but just once last night, since then it will not happen.
Tomcat did get the shutdown request when it happened and tried to shutdown all the webapps (wathcing the logs in real-time). But KeelDirectServer/AbstractServer was stuck waiting for a monitor. Phil any ideas? I didn't keep the thread dump.
When it happened I had all the Keel webapp deploys (nojms-struts/cocoon/velocity, openjms-struts/cocoon/velocity and axis) all present as contexts. I then deleted all but the admin/manager/example webapps and retried and Tomcat shut down properly. Since then I have rebooted the machine. This morning I tried again with the default webapp, but doesn't happen anymore. Steve, can you try a reboot once to see if the condition clears for you. Else, it might have something to do with system load.
Something to keep watch on. Until then kill - 9 <pid> works just fine.
Shash
-- Java/J2EE Developer/Integrator Co-Chair, Dallas/FortWorth J2EE Sig 214-724-7741
http://keelframework.org/documentation Keelgroup mailing list [EMAIL PROTECTED] http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
