[jboss-jira] [JBoss JIRA] (WFLY-6685) Cache container enable statistics can lead to classloader leak
Paul Ferraro (JIRA)
issues at jboss.org
Wed Jun 8 12:47:00 EDT 2016
[ https://issues.jboss.org/browse/WFLY-6685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13249831#comment-13249831 ]
Paul Ferraro commented on WFLY-6685:
------------------------------------
We can work around this issue by preventing Infinispan from attempting to register mbeans for its channel.
MBeans for the channel are already registered by the JGroups subsystem.
> Cache container enable statistics can lead to classloader leak
> --------------------------------------------------------------
>
> Key: WFLY-6685
> URL: https://issues.jboss.org/browse/WFLY-6685
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 10.0.0.Final
> Reporter: Mathieu Lachance
> Assignee: Paul Ferraro
>
> In standalone.xml, if we enable statistics such as:
> {code}
> <cache-container name="web" default-cache="repl" module="org.wildfly.clustering.web.infinispan" statistics-enabled="true">
> <transport lock-timeout="60000"/>
> <replicated-cache name="repl" statistics-enabled="true" mode="ASYNC">
> <locking isolation="READ_COMMITTED"/>
> <transaction locking="OPTIMISTIC" mode="BATCH"/>
> <state-transfer chunk-size="512" timeout="240000"/>
> </replicated-cache>
> </cache-container>
> {code}
> The following MBean:
> {code}
> jboss.infinispan:cluster=web,type=channel
> {code}
> is getting eventually registered when deploying any application.
> When undeploying that application, the MBean is not getting unregistered and thus can leak pretty much anything.
> Also, if you try to deploy the very same application right after another MBean will get registered:
> {code}
> jboss.infinispan2:cluster=web,type=channel
> {code}
> Note: cache enable-statistics=true doesn't seems to leak anything.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jboss-jira
mailing list