[
https://issues.jboss.org/browse/ISPN-3076?page=com.atlassian.jira.plugin....
]
Radim Vansa commented on ISPN-3076:
-----------------------------------
I think that in production the INFO level should be used as the threshold, and log4j can
handle that.
When debugging (tracing), I've experienced contention in log4j locks for many times,
and this contention led to node unresponsiveness and consequential failure.
Log4j2 is not complete cure for that, but it eliminates the bottleneck in logging
framework and leaves us only in synchronization when persisting the data. Therefore, it
allows to implement appender looking as the circular memory buffer.
I don't think that particularly String formatting brings so much overhead.
Infinispan should enable use of log4j2
--------------------------------------
Key: ISPN-3076
URL:
https://issues.jboss.org/browse/ISPN-3076
Project: Infinispan
Issue Type: Enhancement
Affects Versions: 5.2.5.Final, 6.0.0.Final
Environment: Any
Reporter: Divya Mehra
Assignee: Mircea Markus
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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira