Memory leak with Jersey 2.33

Folks, This is probably not a Tomcat issue, but any thoughts on how to resolve this would be greatly appreciated. I am running into an apparent ClassLoader leak with the following configuration: Windows 10 Professional (64 bit, latest updates) OpenJDK 11.0.10 Apache Tomcat 7.0.107 Jersey Re

Re: Memory leak with Jersey 2.33

On 1/31/2021 9:39 PM, Mark Eggers wrote: Folks, This is probably not a Tomcat issue, but any thoughts on how to resolve this would be greatly appreciated. I am running into an apparent ClassLoader leak with the following configuration: Windows 10 Professional (64 bit, latest updates) OpenJ

Re: Memory leak with Jersey 2.33

On 01/02/2021 06:37, Mark Eggers wrote: > On 1/31/2021 9:39 PM, Mark Eggers wrote: >> GC roots for cplanapi are: >> >> class com.sun.naming.internal.ResourceManager >> '- propertiesCache java.util.WeakHashMap >>     '- table java.util.WeakHashMap$Entry[16] >>    '- java.util.WeakHashMap$Entr

Re: Memory leak with Jersey 2.33

Mark, On 2/1/2021 1:33 AM, Mark Thomas wrote: Is the GC root above the only one? I've seen similar behaviour in the past where weak references appear to be the cause of a leak but closer inspection uncovers a strong reference. Mark Thanks for putting me on the correct track. I'm using log4j2