Details
-
Bug
-
Resolution: Done
-
Major
-
7.0.1.CR1
-
None
Description
In standalone.xml, if we enable statistics such as:
<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>
The following MBean:
jboss.infinispan:cluster=web,type=channel
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:
jboss.infinispan2:cluster=web,type=channel
Note: cache enable-statistics=true doesn't seems to leak anything.
Attachments
Issue Links
- clones
-
WFLY-6685 Cache container enable statistics can lead to classloader leak
-
- Closed
-