Home
You cannot shut down Tomcat while keeping the webapp running because Tomcat is the container for the webapp, and when Tomcat shuts down, the entire Tomcat JVM shuts down. However, barring Tomcat bugs, the normal shutdown process will shutdown all the Tomcat-spawned threads. (In reply to comment #4) I'm re-opening this to make this change for 7.0.41 I backported the test case to Tomcat 7 in r1634259. The test case passes successfully. The value that i set to Tomcat's asyncTimeout connector property is ignored when using the APR connector on Windows no matter what (default 10 seconds is used instead). That value is always respected when using the default Http11Protocol connector or the Http11NioProtocol one.
Java Thread Dump Analyser is a tool for quickly summarising lengthy Java thread dumps.
Download
News: 25/10/2012: Add command line version. 08/08/2012: Fixes a bug which caused the last thread in a thread dump to be ignored.
Tomcat Async Timeout
- jtda.jar (Windows/Linux)
- JTDA.app.tar (OSX)
- jtda-cli.jar (Windows/Linux/OSX)
The Problem
One of the common types of diagnostics which a Java developer has to look at as a Thread Dump. This lists the stack trace of all the threads in the JVM. However, the generated output can be really tedious to scan through as some applications (e.g. Webapp containers such as Tomcat) can use hundreds of threads, many of which will have the same stack trace as they are idle threads waiting for work.
The Solution
To make it easier to understand the contents of a Java thread dump you can use the Java Thread Dump Analyser. All you have to do is copy/paste your thread dump text into the input tab and press the Analyse button.
Here is an example of the output which is generated.
Loading a file
jtda.jar can be used to load a file on Windows/Linux: Drupal social media.
Command Line Version
jtda-cli.jar can be used at the command line to perform the same thread dump summarization as the GUI.
Asynctimeout Tomcat
Download
News: 25/10/2012: Add command line version. 08/08/2012: Fixes a bug which caused the last thread in a thread dump to be ignored.
Tomcat Async Timeout
- jtda.jar (Windows/Linux)
- JTDA.app.tar (OSX)
- jtda-cli.jar (Windows/Linux/OSX)
The Problem
One of the common types of diagnostics which a Java developer has to look at as a Thread Dump. This lists the stack trace of all the threads in the JVM. However, the generated output can be really tedious to scan through as some applications (e.g. Webapp containers such as Tomcat) can use hundreds of threads, many of which will have the same stack trace as they are idle threads waiting for work.
The Solution
To make it easier to understand the contents of a Java thread dump you can use the Java Thread Dump Analyser. All you have to do is copy/paste your thread dump text into the input tab and press the Analyse button.
Here is an example of the output which is generated.
Loading a file
jtda.jar can be used to load a file on Windows/Linux: Drupal social media.
Command Line Version
jtda-cli.jar can be used at the command line to perform the same thread dump summarization as the GUI.
Asynctimeout Tomcat
To see the usage:
To perform the standard summarization:
