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 On Jun 6, 2014, at 10:43 AM, Ulavapalli, Prashant <[email protected]> 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 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 > log4j-api-2.0-rc1.jar > log4j-core-2.0-rc1.jar > > In the war, I am deploying. > > Also have replace/removed log4j 1.2 with the above jars in > > jboss_home/client/ > jboss_home/common/lib > > > Is there anything else I am missing? > > Any help is much appreciated. > > Thanks > -prash --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
