[
https://issues.jboss.org/browse/JGRP-1585?page=com.atlassian.jira.plugin....
]
David Lloyd commented on JGRP-1585:
-----------------------------------
We support all of those, except for #6 (though I am pretty sure we can add that). (Also -
log4j2 seriously doesn't support runtime level changes? Yikes...)
Actually #5 is actually a "so-so" kind of thing. To support the i18n stuff
we're supposed to support, you do need one additional compile-time-only JAR, but it
uses Javac's built-in and standard annotation processing mechanism, so it works fine
even if you just run javac on the command line. If you do not use the i18n mechanism
though, that part is completely optional. But beyond that, it's just one JAR at
runtime (plus the backend of choice, if it != JUL).
Upgrade log4j
-------------
Key: JGRP-1585
URL:
https://issues.jboss.org/browse/JGRP-1585
Project: JGroups
Issue Type: Task
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 3.4
log4j has some heavy synchronization, which can sometimes lead to code blocking up to 30
seconds (see [1]).
Investigate whether we should switch to log42 [2]. Perhaps we can simply program against
the API (30K) and not even ship the implementation ?
[1]
https://issues.apache.org/bugzilla/show_bug.cgi?id=51047
[2]
http://logging.apache.org/log4j/2.x/
--
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