https://issues.apache.org/bugzilla/show_bug.cgi?id=51467
--- Comment #6 from Sylvain Laurent 2011-07-04 18:50:13
UTC ---
It seems there used to be call to DedicatedThreadExecutor.executeInOwnThread()
but r1087715 changed it to create a new Thread :
http://svn.apache.org/viewvc/tomcat/trunk/java/
https://issues.apache.org/bugzilla/show_bug.cgi?id=51467
Mark Thomas changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://issues.apache.org/bugzilla/show_bug.cgi?id=51467
--- Comment #4 from Christopher Schultz
2011-07-03 18:41:59 UTC ---
Rainer,
Aah, I didn't look far enough up in the code to see that comment: thanks for
clarifying.
Without running Thread.start(), I believe any ThreadLocals registered wi
https://issues.apache.org/bugzilla/show_bug.cgi?id=51467
--- Comment #3 from Rainer Jung 2011-07-03 17:45:23
UTC ---
Re Comment #2: http://svn.apache.org/viewvc?view=revision&revision=1044145
Log says:
bug 49159: Improve ThreadLocal memory leak clean-up
https://issues.apache.org/bugzilla/show
https://issues.apache.org/bugzilla/show_bug.cgi?id=51467
--- Comment #2 from Christopher Schultz
2011-07-03 16:43:45 UTC ---
I'm wondering why the whole process is run in a Thread in the first place. If
the thread is start()ed, when immediately join()ed, and all exceptions are
documented not to
https://issues.apache.org/bugzilla/show_bug.cgi?id=51467
--- Comment #1 from Felix Schumacher
2011-07-03 10:20:20 UTC ---
Created attachment 27245
--> https://issues.apache.org/bugzilla/attachment.cgi?id=27245
use start instead of run to start a thread
--
Configure bugmail: https://issues.ap
