[
https://issues.jboss.org/browse/ISPN-3076?page=com.atlassian.jira.plugin....
]
Sanne Grinovero commented on ISPN-3076:
---------------------------------------
Sorry my statement had a critical typo: I meant to say
{quote}But I still don't get why Log4j*2* is of any interest to us.{quote}
In other words, I think JBoss Logging should be our default logger implementation, and we
also support log4j (v1) because it's a popular choice in other containers.
Log4j V2 is not that popular yet to make this a wise move, especially until it has proven
itself more efficient: I don't think we have data to back this up, for sure it defeats
the purpose of even considering Log4J which should be "going with the popular
version".
Very interesting of course to explore alternatives, for debugging purposes for example we
could have an in memory circular buffer which skips the String formatting step: just store
the parameters as they are together with the log id, the buffer content could then be
"rendered" in its string form at a second time when and only if needed.
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