[infinispan-issues] [JBoss JIRA] (ISPN-6375) Metaspace memory leak with infinispan
Dan Berindei (Jira)
issues at jboss.org
Fri Jan 17 03:45:43 EST 2020
[ https://issues.redhat.com/browse/ISPN-6375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Berindei resolved ISPN-6375.
--------------------------------
Fix Version/s: 9.0.0.Final
Resolution: Out of Date
Fixed when we removed {{EquivalentConcurrentHashMapV8}} and replaced it with Caffeine.
> Metaspace memory leak with infinispan
> -------------------------------------
>
> Key: ISPN-6375
> URL: https://issues.redhat.com/browse/ISPN-6375
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Affects Versions: 8.1.2.Final
> Reporter: Andrej Dmitrenko
> Priority: Major
> Fix For: 9.0.0.Final
>
> Attachments: memory-analyzer.png
>
>
> I use infinispan for embedded cache and criteria query in cache. It is works great!
> I start infinispan in my application and call embeddedCacheManager.stop() at application destroy.
> I run my application in oracle weblogic 12.1.3 server. And after redeploy my application I see metaspace memory leak.
> I have checked heap dump in memory analizer.
> The cause in thread local variable threadCounterHashCode in org.infinispan.commons.util.concurrent.jdk8backported.EquivalentConcurrentHashMapV8$CounterHashCode class
> After undeploy aplication there is a thread which keep thread local reference to threadCounterHashCode, and threadCounterHashCode keep link to classloader and that's why classloader cannot be removed from metaspace memory.
> I cannot control this thread.
> I have got suggestion in forum to create ticket in JIRA (https://developer.jboss.org/message/952848)
> Please do something with class org.infinispan.commons.util.concurrent.jdk8backported.EquivalentConcurrentHashMapV8$CounterHashCode to avoid metaspace memory leak in cases when user does not control thread pool
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
More information about the infinispan-issues
mailing list