[
https://issues.jboss.org/browse/ISPN-3076?page=com.atlassian.jira.plugin....
]
Radim Vansa commented on ISPN-3076:
-----------------------------------
And regarding overengineered async appender: In practice, I've found that async
appender is really no cure for trace logging in infinispan, as the logging will be always
faster than writing the logs down and eventually we will only synchronize on the writing
queue, but the problems with stuck logging during tracing won't go away. Before Xmas I
was working on a modified version of async appender that would slow down the system but
never pause it for more than few ms, nor make ST unbearably slow.
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