On Wed, Mar 21, 2012 at 7:52 AM, Pid * <p...@pidster.com> wrote: > On 21 Mar 2012, at 02:41, Dale Ogilvie <dale_ogil...@trimble.com> wrote:
> >> When the application is unloaded by Tomcat, it >> should go away completely, regardless of (for example) unstopped threads >> in library foo. > > There is an aggressive thread killer option but it is unreliable, > because it is hard to stop a Java thread from outside the thread. How about having an explicit executor pool per webapp? That would allow to throw this pool away on reload, and prevent pollution of general thread pool by one-webapp's thread locals. Leon --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
