atom feed4 messages in org.apache.tomcat.devMemory leak found in java.util.concur...
FromSent OnAttachments
Mark ThomasJan 9, 2017 12:58 pm 
Konstantin KolinkoJan 21, 2017 1:31 am 
Mark ThomasJan 21, 2017 8:56 am 
Rory O'DonnellJan 23, 2017 1:40 am 
Subject:Memory leak found in java.util.concurrent.ForkJoinPool
From:Mark Thomas (mar@apache.org)
Date:Jan 9, 2017 12:58:38 pm
List:org.apache.tomcat.dev

All,

As a result of a thread on the users list, a memory leak has been discovered in java.util.concurrent.ForkJoinPool.commonPool. It appears that use of this pool is hard-coded in multiple places such as Collection.parallelStream().forEach().

I have some ideas about how to work-around the leaks with JreMemoryLeakPreventionListener but any code that depends on the Tomcat class loader being set (e.g. JNDI lookup) is going to break if the user tries to use Collection.parallelStream().

Rory,

The review Id for my report is 9046841. Anything you can do to get this accepted and in front of the right folks to fix it would be appreciated.

Kind regards,

Mark