[
https://issues.jboss.org/browse/ISPN-3076?page=com.atlassian.jira.plugin....
]
Dan Berindei commented on ISPN-3076:
------------------------------------
I've stopped working on it. You could try implementing your own {{CustomLogFactory}}
to use {{LogManager.getLogger(clazz)}} instead of
{{LogManager.getFormattedLogger(clazz)}}, as Bela suggested.
Infinispan should enable use of log4j2
--------------------------------------
Key: ISPN-3076
URL:
https://issues.jboss.org/browse/ISPN-3076
Project: Infinispan
Issue Type: Enhancement
Components: Core
Affects Versions: 5.2.5.Final, 6.0.0.Final
Environment: Any
Reporter: Divya Mehra
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
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)