[
https://issues.jboss.org/browse/ISPN-3076?page=com.atlassian.jira.plugin....
]
Dan Berindei commented on ISPN-3076:
------------------------------------
Thanks Bela, for now the blocker is in jboss-logging. I may try to switch the
jboss-logging backend to JDK logging and/or jboss-logmanager (in which case your
CustomLogFactory will come in handy).
Infinispan should enable use of log4j2
--------------------------------------
Key: ISPN-3076
URL:
https://issues.jboss.org/browse/ISPN-3076
Project: Infinispan
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Core
Affects Versions: 5.2.5.Final, 6.0.0.Final
Environment: Any
Reporter: Divya Mehra
Assignee: Dan Berindei
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.2.6#6264)