[jboss-jira] [JBoss JIRA] (JGRP-1585) Upgrade log4j

[Bela Ban (JIRA)]

    [ https://issues.jboss.org/browse/JGRP-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761228#comment-12761228 ] 

Bela Ban commented on JGRP-1585:
--------------------------------

Hi David,

here are my requirements:
# Add vararg log methods to Log [1], e.g. trace(String format, Object... params);
# Replace log4j, possible candidates so far:
## log4j2
## jboss-logging
# I currently support JUL and log4j as backends, and these need to be supported. If more backends can be supported, even better
# Minimize the number of JARs to be used
# No pre-processing phase (mvn or ant)
# Ability to change the log level at runtime. This is an issue for log4j2, which doesn't support this anymore. It's not enough to be able to periodically reparse the config file, as I want to do this across a cluster, via probe.sh op=UDP.setLevel["trace"]

If you tell me that I need only 1 JAR (plus the backend, but that's up to the deployer), than that sounds appealing. I looked at jboss-logging on GitHub, but am unsure which project I should use there. Do you have documentation on jboss-logging ? I googled, but I think I hit old documentation...


[1] https://github.com/belaban/JGroups/tree/master/src/org/jgroups/logging
[2] https://github.com/jboss-logging
                
> 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