Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-4925

Cache container enable statistics can lead to classloader leak

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.1.0.DR3
    • 7.0.1.CR1
    • Clustering
    • None
    • Hide
      1. in standalone.xml enable the statistics on the web cache container
      2. deploy a basic application
      3. undeploy the application
      4. observes that the MBean is still registered
      5. re-deploy the application
      6. observes the MBean is still registered and a new MBean is getting registered
      Show
      in standalone.xml enable the statistics on the web cache container deploy a basic application undeploy the application observes that the MBean is still registered re-deploy the application observes the MBean is still registered and a new MBean is getting registered

      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.

              spyrkob Bartosz Spyrko-Smietanko (Inactive)
              pferraro@redhat.com Paul Ferraro
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: