https://issues.apache.org/bugzilla/show_bug.cgi?id=56583
Bug ID: 56583 Summary: Classloader leak in AsyncAppender Product: Log4j Version: unspecified Hardware: PC OS: Mac OS X 10.4 Status: NEW Severity: normal Priority: P2 Component: Appender Assignee: log4j-dev@logging.apache.org Reporter: nik...@plumbr.eu AsyncAppender starts a Dispatcher thread, but I was unable to find any hints about when and how this thread should stop. Leaving this thread running after web application undeploy will create a classloader leak. In addition to that, AsyncAppender uses protected boolean closed field to communicate, that appender is now closed and so Dispatcher thread should stop. But this field is not volatile, set from one thread and is read from another thread. Which does not work and may be one of the reasons of the leak in the first place. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org