xin.brradish.liu created LOG4J2-2354:
----------------------------------------
Summary: log4j-jcl cause memery leak in TomCat 8.5.24
Key: LOG4J2-2354
URL: https://issues.apache.org/jira/browse/LOG4J2-2354
Project: Log4j 2
Issue Type: Bug
Components: JCL Bridge
Affects Versions: 2.11.0
Reporter: xin.brradish.liu
I build a skeleton Spring MVC project to test this.
here is my whole dependencies in pom.xml:
{code:java}
<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>
{code}
when undeploy or stop of the Application in TomCat,I got this:
{code:java}
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
{code}
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?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
