One use case I had for this feature is to see which threads were preventing the Tomcat JVM from shutting down because they're not daemons. (Java 5 jconsole gives a total count but doesn't show which ones are daemons.) So, I wanted to hit the stack dump button after hitting the stop button. If Tomcat had a stack dump button, IDEA might disable it by then because it thinks that Tomcat has finished shutting down (even though its JVM continues to run).
This leads me to perhaps a separate issue. I had to open the Windows task manager to see whether or not the Tomcat JVM had really exited. If I start Tomcat again without killing the last JVM, bad things happen, due to lack of resources I assume. It would be much better if IDEA showed me that the Tomcat JVM has not exited, and gave me the option of killing the JVM process at that point (or suggest looking for non-daemon threads).
David Beutel - 27 Feb 07 21:50 One use case I had for this feature is to see which threads were preventing the Tomcat JVM from shutting down because they're not daemons. (Java 5 jconsole gives a total count but doesn't show which ones are daemons.) So, I wanted to hit the stack dump button after hitting the stop button. If Tomcat had a stack dump button, IDEA might disable it by then because it thinks that Tomcat has finished shutting down (even though its JVM continues to run).
This leads me to perhaps a separate issue. I had to open the Windows task manager to see whether or not the Tomcat JVM had really exited. If I start Tomcat again without killing the last JVM, bad things happen, due to lack of resources I assume. It would be much better if IDEA showed me that the Tomcat JVM has not exited, and gave me the option of killing the JVM process at that point (or suggest looking for non-daemon threads).
New Feature
Open
Normal
There is no print stacktrace button in run web app configuration. Nice to have one
This leads me to perhaps a separate issue. I had to open the Windows task manager to see whether or not the Tomcat JVM had really exited. If I start Tomcat again without killing the last JVM, bad things happen, due to lack of resources I assume. It would be much better if IDEA showed me that the Tomcat JVM has not exited, and gave me the option of killing the JVM process at that point (or suggest looking for non-daemon threads).