https://issues.apache.org/bugzilla/show_bug.cgi?id=49414
--- Comment #2 from Marc Guillemot <mguille...@yahoo.fr> 2010-06-14 03:20:42 EDT --- (In reply to comment #1) > Tomcat already waits (I think 20s is the default) for requests to complete > before shutting down the webapp. ??? If you run the provided unit test, you will see that Tomcat doesn't wait 20 secondes for requests to complete. > A still running request, particularly if deadlocked, would trigger a memory > leak so I think this is something that the leak detection should be reporting. > I agree a better message is required to make clear the correct root cause in > this scenario. I don't have any strong feelings at this point as to the best > way to go. At first glance a ThreadGroup looks reasonable. Thinking at it again, it would surely not be bad to have a "Tomcat ThreadGroup" but it wouldn't solve the problem here: user Threads started from a webapp without a specified ThreadGroup would belong to the Tomcat ThreadGroup too. In this case it wouldn't help to distinguish "Tomcat threads" from "user threads". -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
