[
https://issues.jboss.org/browse/JGRP-1585?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-1585:
--------------------------------
log4j2:
* Requires 2 JARs: API and CORE
** We could copy the required API code (mainly LogManager.getLogger()) into JGroups's
LogFactory ...
* The level cannot be set at runtime, unless we downcast the Logger to its implementation
class (setting the level is not exposed in the interface).
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