I was trying to upgrade to log4j2 myself for JBOSS 5. And seem to running into
issues. Somehow JBOSS 5 is not recognizing the changes I made.
By default I guess JBOSS uses there jbosslogging and somehow I am not able to
tie in log4j2 to it.
I have added
log4j-1.2-api-2.0-rc1.jar
I believe log4j2 support was added to a more recent version of
jboss-logging.
On 6 June 2014 12:43, Ulavapalli, Prashant
prashant.ulavapa...@digitalinsight.com wrote:
I was trying to upgrade to log4j2 myself for JBOSS 5. And seem to running
into issues. Somehow JBOSS 5 is not recognizing the
I seem to recall having to remove a jbosslogging jar as it had its own SLF4J
binding in it. Plus there was a bug that they didn’t define one of the JUL log
levels and it would throw an exception. But I haven’t looked at Jboss
integration in about a year so the exact details are sketchy.
Ralph
I see this exception
Caused by: java.lang.SecurityException: class
org.slf4j.helpers.Log4jLoggerFactory's signer information does not match
signer information of other classes in the same package
at java.lang.ClassLoader.checkCerts(ClassLoader.java:812)
at
