[LOG4J2-2354] log4j-jcl cause memery leak in TomCat 8.5.24

• Type: Bug
• Status: Open
• Priority: Critical
• Resolution: Unresolved
• Affects Version/s: 2.11.0
• Component/s: JCL Bridge
• Labels: newbie
• Assignee: Unassigned
• Reporter: brradish
• Created: 18/Jun/18 09:41
• Updated: 02/Jul/18 21:07

Description

I build a skeleton Spring MVC project to test this.

here is my whole dependencies in pom.xml:

<dependencies>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-context</artifactId>
<version>5.0.7.RELEASE</version>
</dependency>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-webmvc</artifactId>
<version>5.0.7.RELEASE</version>
</dependency>
<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-jcl</artifactId>
<version>2.11.0</version>
</dependency>
<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-web</artifactId>
<version>2.11.0</version>
</dependency>
</dependencies>

when undeploy or stop of the Application in TomCat,I got this:

The following web applications were stopped (reloaded, undeployed), but their
classes from previous runs are still loaded in memory, thus causing a memory
leak (use a profiler to confirm):
/myapp

I also test this in Spring 4.2.0 . It's the same result.

 

I am a beginner in log4j2, Is there something I missed? or it's indeed a bug?