Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-2716

Redeploy of a WAR results in ClassLoader leak when a logging-profile is enabled

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • 8.0.0.CR1
    • None
    • Logging
    • None
    • Hide

      You can use the same logone.war and configuration attached in WFLY-2524. And repeat the following commands to deploy and undeploy.

      $JBOSS_HOME/bin/jboss-cli.sh -c "deploy --force target/logone.war" 
curl -s http://localhost:8080/logone/HogeServlet
jcmd $JBOSSPID GC.class_histogram | grep --color -E 'ClassLoader' 
jstat -gc $JBOSSPID
      Show
      You can use the same logone.war and configuration attached in WFLY-2524 . And repeat the following commands to deploy and undeploy. $JBOSS_HOME/bin/jboss-cli.sh -c "deploy --force target/logone.war" curl -s http: //localhost:8080/logone/HogeServlet jcmd $JBOSSPID GC.class_histogram | grep --color -E ' ClassLoader ' jstat -gc $JBOSSPID

      Web app's ModuleClassLoader is not released even after its undeployment. It seems contextMap of org.jboss.logmanager.ClassLoaderLogContextSelector object is holding the class loader's reference. If no logging-profile is configured, it doesn't leak.

              jperkins-rhn James Perkins
              rhn-support-onagano Osamu Nagano
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: