https://issues.apache.org/bugzilla/show_bug.cgi?id=49414
--- Comment #1 from Mark Thomas <ma...@apache.org> 2010-06-13 16:28:45 EDT --- Tomcat already waits (I think 20s is the default) for requests to complete before shutting down the webapp. 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. -- 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
