Tomcat thread blocking
Hi, I've recently observed a scenario in Tomcat 6.0.13 64-bit under SUN JDK 1.6_03 (x64 Windows platform), where a large number of threads show a status of BLOCKED. Can someone please advise the easiest and most effective way of helping identify the original cause of the block?or have I just opened up a can of worms?! The behaviour is not something I can replicate so I need a method for in situ investigation, before I have to restart Tomcat to restore service (after a while Tomcat consumes too much CPU and becomes unresponsive) Any pointers would be much appreciated. Darren Kukulka Business Applications Architect Connaught PLC Tel: 01392 353497 Business in the Community (BiTC) Team of the Year 2008 for Community Impact RoSPA Gold Awards - Connaught now have 15 in total Winner of Partnering Contractor of the Year Award in 2005 and 2007 Tenant Care Scheme of the Year 2007 Please visit our website to see a full list of Connaught's Registered Companies www.connaught.plc.uk/Investors/Registered-Companies Disclaimer: The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete this message. Connaught plc, Head Office 01392 444546
Re: Tomcat thread blocking
Darren Kukulka wrote: Hi, I've recently observed a scenario in Tomcat 6.0.13 64-bit under SUN JDK 1.6_03 (x64 Windows platform), where a large number of threads show a status of BLOCKED. Can someone please advise the easiest and most effective way of helping identify the original cause of the block?or have I just opened up a can of worms?! Get 2 or 3 thread dumps ~20secs apart and analyse them. The behaviour is not something I can replicate so I need a method for in situ investigation, before I have to restart Tomcat to restore service (after a while Tomcat consumes too much CPU and becomes unresponsive) Thread dumps can be generated whilst Tomcat is running. Mark - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat thread blocking
- Original Message - From: Darren Kukulka [EMAIL PROTECTED] To: users@tomcat.apache.org Sent: Wednesday, September 24, 2008 9:37 AM Subject: Tomcat thread blocking Hi, I've recently observed a scenario in Tomcat 6.0.13 64-bit under SUN JDK 1.6_03 (x64 Windows platform), where a large number of threads show a status of BLOCKED. Can someone please advise the easiest and most effective way of helping identify the original cause of the block?or have I just opened up a can of worms?! The behaviour is not something I can replicate so I need a method for in situ investigation, before I have to restart Tomcat to restore service (after a while Tomcat consumes too much CPU and becomes unresponsive) Any pointers would be much appreciated. == Google for VisualVM... its in the later Java versions Heap Dumps, Thread Dumps... its like JConsole on steroids ;) --- HARBOR : http://www.kewlstuff.co.za/index.htm The most powerful application server on earth. The only real POJO Application Server. See it in Action : http://www.kewlstuff.co.za/cd_tut_swf/whatisejb1.htm --- - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
