https://issues.apache.org/bugzilla/show_bug.cgi?id=49159
--- Comment #7 from Pid <pids...@apache.org> 2010-09-23 17:55:09 EDT --- (In reply to comment #6) > Pid, I applied your patch but it does not work. > Actually when the thread calls join(0) on itself it just leads to a deadlock : > the Thread will remain forever in the join method unless it is interrupted. It's experimental admittedly. I'll clean up my SVN repo & retry it, thought it was working... If it won't work at all, then the idea is dead, but there must be a way to terminate an individual thread & remove it from the pool. > Furthermore your idea works only if a new context is started. Or an existing one is restarted, the point is that it's a compromise. The idea was to have a lower impact than restarting the whole thread pool. > If a context is stopped and no other context is started, Threads won't be > renewed. If a context is stopped and no other context is started, how will the server work? -- 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
