[
https://issues.jboss.org/browse/ISPN-3076?page=com.atlassian.jira.plugin....
]
Serge SIMON commented on ISPN-3076:
-----------------------------------
Any news about this subject ?
I'm too struggling with jboss logging and Log4J2.
My classpath is supposed to be correct (log4j2 api + core + bridges + jboss logging
3.2.0.Final - and no log4j 1 jar) and the only last logs not working are those ones with
the exact same message :
{quote}
2015-01-08 08:56:28,421 WARN The Logger
org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher was created with the
message factory org.apache.logging.log4j.message.ParameterizedMessageFactory@59aea098 and
is now requested with the message factory
org.apache.logging.log4j.message.StringFormatterMessageFactory@57b18927, which may create
log events with unexpected formatting.
{quote}
Or is there a working workaround ?
Infinispan should enable use of log4j2
--------------------------------------
Key: ISPN-3076
URL:
https://issues.jboss.org/browse/ISPN-3076
Project: Infinispan
Issue Type: Enhancement
Components: Core
Affects Versions: 5.2.5.Final, 6.0.0.Final
Environment: Any
Reporter: Divya Mehra
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.3.11#6341)