the problem is not comming log4j. It's a jboss classloading problem.
In jboss4.3 sp1 version, you could have a log4j.jar version for each of you application.
But with jboss 4.2 version doing so, you may experience with exception below
| log4j:ERROR A "org.jboss.logging.appender.FileAppender" object is not
assignable to a "org.apache.log4j.Appender" variable.
| log4j:ERROR The class "org.apache.log4j.Appender" was loaded by
| log4j:ERROR [WebappClassLoader
| delegate: false
| repositories:
| /WEB-INF/classes/
| ----------> Parent Classloader:
| java.net.FactoryURLClassLoader@18c10af
| ] whereas object of type
| log4j:ERROR "org.jboss.logging.appender.FileAppender" was loaded by
[org.jboss.system.server.NoAnnotationURLClassLoader@1a33d48].
| log4j:ERROR Could not instantiate appender named "FILE".
|
It seem not possible to override jboss server librairies (log4j.jar is present in jboss
server lib and has been customised).
Even if you try to isolate classloadiing, it's not working witk log4j.
Meissa
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058623#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...