[infinispan-issues] [JBoss JIRA] (ISPN-3076) Infinispan should enable use of log4j2

[Dan Berindei (JIRA)]

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

Dan Berindei commented on ISPN-3076:
------------------------------------

I'm suspending my investigations for now, as initial results are not encouraging: jboss-logging support for log4j2 is broken in the latest release, 3.2.0.Beta1: JBLOGGING-107.

There is another pain point with JGroups using a different {{MessageFactory}} than jboss-logging and log4j2 spitting out this kind of errors:

{noformat}
2014-08-05 20:15:46,408 WARN The Logger org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher was created with the message factory org.apache.logging.log4j.message.ParameterizedMessageFactory at 6208e6d9 and is now requested with the message factory org.apache.logging.log4j.message.StringFormatterMessageFactory at 10be3e37, which may create log events with unexpected formatting.
{noformat}

It appears in log4j2 calling {{LogManager.getLogger(clazz)}} (the way jboss-logging does), {{LogManager.getFormattedLogger(clazz)}} (the way JGroups does) should give you different loggers, but they both register the loggers with the same name, so they always return the first logger. That breaks message formatting for users that expect the second, so log4j2 gives that warning every time we create a new CommandAwareRpcDispatcher (and maybe other classes that extend JGroups classes).

> Infinispan should enable use of log4j2
> --------------------------------------
>
>                 Key: ISPN-3076
>                 URL: https://issues.jboss.org/browse/ISPN-3076
>             Project: Infinispan
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: Core
>    Affects Versions: 5.2.5.Final, 6.0.0.Final
>         Environment: Any
>            Reporter: Divya Mehra
>            Assignee: Dan Berindei
>
> 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 was sent by Atlassian JIRA
(v6.2.6#6264)