[ https://issues.jboss.org/browse/ISPN-3076?page=com.atlassian.jira.plugin.... ] 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@6208e6d9 and is now requested with the message factory org.apache.logging.log4j.message.StringFormatterMessageFactory@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). -- This message was sent by Atlassian JIRA (v6.2.6#6264)