How to Configure WebSphere Application Server hung thread detector to automatically produce javacores or thread dump

When ever Websphere Application Server has a thread that runs for a long time (600s), by default it will report with a WSVR0605W message. This is a similar behvaiour we see in weblogic. WSVR0605W: Thread has been active for and may be hung. There are in total in the server that may be hung. Reading from the following source, it is possible to get Websphere Application Server to generate a javacore when a potentially hung thread is reported. On Solaris, we call this thread dump. Source : [http://www-01.ibm.com/support/docview.wss?uid=swg21448581] This core file can be helpful in troubleshooting server hangs and performance issues. If the jobs running in your system usually take a long time, you may want to tune the monitoring time to more than 600s else you might get false reports. The website described that property "com.ibm.websphere.threadmonitor.dump.java" should be enabled. h4. Steps to enable auto thread dump. Log in to administrative console, click Servers > Application Servers > server_name. Under Server Infrastructure, click Administration > Custom Properties. Click New. Add the following property: Name: com.ibm.websphere.threadmonitor.dump.java Value: true Click Apply. Click OK and save the configuration changes. Restart the Application Server for the changes to take effect. done. In case you want to manually trigger a thread dump, try kill -3 .