-
Enhancement
-
Resolution: Done
-
Major
-
5.2.5.Final, 6.0.0.Final
-
None
log4j locks up on a certain amount of load, especially under concurrent access. The recommendation was to move up to log4j2. This can be done by removing
1 JAR (log4j.jar) and adding 2 JARs (log4j-bridge and log4j-core.jar).
Also refer: https://issues.jboss.org/browse/ISPN-2976
- is blocked by
-
JBLOGGING-107 JBoss Logging throws NullPointerException when used with Log4j 2.0 final.
- Resolved
-
JBLOGGING-94 JBoss Logging does not detect log4j 2.0
- Resolved
-
JBLOGGING-95 Add Logger/LoggerProvider to support new Log4j 2 to improve performance
- Resolved