jalkanen/speed4j — Issue #18: Tomcat 7.0.23 reports PeriodicalLog as a possible source for memory leak on application reload
Author: pcting
Created: 2012-03-07 09:00:40+00:00
State: open

When I deploy a WAR which have classes leveraging speed4j, I get the following logged message from Tomcat:
...
SEVERE: The web application [/redirector] appears to have started a thread named [Speed4J PeriodicalLog Collector Thread] but has failed to stop it. This is very likely to create a memory leak.
...

Looking at the PeriodicalLog code, I suppose all that's needed is something to wire into Tomcat events to stop the thread.