DO NOT REPLY [Bug 48895] WebAppClassLoader.clearThreadLocalMap() concurrency issues

2010-10-27 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=48895 --- Comment #4 from quartz 2010-10-27 15:32:18 EDT --- If the only threads accessing the instances of a context are the connector's threads, and if you kill those threads when you remove a context, then you cannot have a leak. Sadly, tomca

DO NOT REPLY [Bug 48895] WebAppClassLoader.clearThreadLocalMap() concurrency issues

2010-04-20 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=48895 Mark Thomas changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

DO NOT REPLY [Bug 48895] WebAppClassLoader.clearThreadLocalMap() concurrency issues

2010-03-29 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=48895 --- Comment #2 from sylvain.laur...@gmail.com 2010-03-29 17:09:43 UTC --- Thanks for the change. So, I guess now we can safely clean thread locals only in threads controlled by tomcat (i.e. worker threads) and by one of these 2 methods : - e

DO NOT REPLY [Bug 48895] WebAppClassLoader.clearThreadLocalMap() concurrency issues

2010-03-29 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=48895 --- Comment #1 from Mark Thomas 2010-03-29 15:04:58 UTC --- This has been fixed in trunk and proposed for 6.0.x -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: