https://issues.apache.org/bugzilla/show_bug.cgi?id=49905
Mark Thomas changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://issues.apache.org/bugzilla/show_bug.cgi?id=49905
--- Comment #1 from Mark Thomas 2010-10-01 12:35:02 EDT ---
This has been fixed in trunk and will be included 7.0.3 onwards.
I have proposed the same fix for 6.0.x.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?t
https://issues.apache.org/bugzilla/show_bug.cgi?id=49905
Summary: In cluster, when using DeltaManager memory leak can
occur
Product: Tomcat 6
Version: 6.0.29
Platform: PC
OS/Version: Windows Server 2003
Status: NEW
On 09/09/2010 12:11, Ruslan Gainutdinov wrote:
>> Proposed solution - implement java.util.concurrent.ThreadFactory in
>> MessageDispatch15Interceptor
>> and pass instance on ThreadPoolExecutor executor creation.
>
> I`ve created patch for proposed solution.
> http://huksley.sdot.ru/wp-content/uplo
> Proposed solution - implement java.util.concurrent.ThreadFactory in
> MessageDispatch15Interceptor
> and pass instance on ThreadPoolExecutor executor creation.
I`ve created patch for proposed solution.
http://huksley.sdot.ru/wp-content/uploads/2010/09/tomcat-fix-memory-leak-deltamanager.zip
Wit
Tested on apache-tomcat-6.0.29 running under jdk 1.6.0_18.
When DeltaManager is instantiated and assigned in StandardContext.start(),
is it done AFTER StandardContext.bindThreads().
DeltaManager, in turn, during initalization, asks for sessions in other nodes,
and this may result in creating thre
