]
James Perkins commented on JBLOGGING-118:
-----------------------------------------
Another option that would avoid using a custom jboss-logging library would be to implement
the
[{{org.jboss.logging.LoggingProvider}}|https://github.com/jamezp/jboss-logging/blob/master/src/main/java/org/jboss/logging/LoggerProvider.java]
as a
[
Subclass of java.util.logging.Level creates PermGen memory leak
---------------------------------------------------------------
Key: JBLOGGING-118
URL:
https://issues.jboss.org/browse/JBLOGGING-118
Project: JBoss Logging
Issue Type: Bug
Components: jboss-logging-jdk
Affects Versions: 3.3.0.Beta1
Environment: JDK7, Tomcat 7, OpenJPA-2.4.1, ValidationAPI-1.x,
hibernate-validator-5.2.1, jboss-logging (fresh from github).
Reporter: Murmur Murmur
Assignee: James Perkins
Subclass of java.util.logging.Level creates PermGen memory leak if webapp provides
jboss-logging.jar inside a webapp. This happen most likely in Tomcat and hot-redeployment
stops working after few times out of PermGen memory.
It's a commonly known side effect of JDK logging library, projects should not inherit
Level class.
See this discussion and github pull request where I have fixed this problem.
http://stackoverflow.com/a/32412984/185565
https://github.com/jboss-logging/jboss-logging/pull/21