log4j within a WAR broke on 4.0.4.GA?

[asack]

My war that worked perfectly fine on 4.0.4.CR2 loads but spews the following error on the GA release:

17:00:17,876 ERROR [STDERR] log4j:ERROR A "org.jboss.logging.util.OnlyOnceErrorHandler" object is not assignable to a "org.apache.log4j.spi.ErrorHandler" variable.
17:00:17,876 ERROR [STDERR] log4j:ERROR The class "org.apache.log4j.spi.ErrorHandler" was loaded by
17:00:17,876 ERROR [STDERR] log4j:ERROR [WebappClassLoader
delegate: false
repositories:
/WEB-INF/classes/
----------> Parent Classloader:
java.net.FactoryURLClassLoader@1e83b01
] whereas object of type
17:00:17,876 ERROR [STDERR] log4j:ERROR "org.jboss.logging.util.OnlyOnceErrorHandler" was loaded by [org.jboss.system.server.NoAnnotationURLClassLoader@1b4fad5].
17:00:17,976 ERROR [STDERR] log4j:ERROR Could not create an Appender. Reported error follows.
17:00:17,976 ERROR [STDERR] java.lang.ClassCastException: org.jboss.logging.appender.DailyRollingFileAppender
.
.
.


My war does ship commons-logging and log4j in its WEB-INF/lib directory. Can someone give me a clue on what's changed?

Thanks!

[asack]

Nobody has run into this yet? Again CR2 worked great but not GA just fails.

[bkrywucki]

asack, I too have experienced the same issue. I will be happy to post a solution if I find one and would appreciate the same.

Thanks

[mt-rac]

Had the same problem with a WAR that ran happily in 4.0.3.

Got round the problem by recompiling with the JBoss-provided log4j jar and removing the log4j jar (which was labelled as 1.2.13 by the way) from my WAR.

I'm not sure if log4j is the root cause or just a symptom ... will try some more tests later.

Martin

[neggs]

I assume that the JBoss Log4j is log4j-boot.jar?

Many thanks.

[mt-rac]

No - log4j.jar supplied in the server lib directory

[rtselvan]

The above error can be fixed by replacing the commons-logging.jar with the commons-logging-1.0.4.jar. It seems that web module is expecting a newer version of the jar

[trautw]

Please remove commons-logging and log4j Jars from your application. Then the JBoss jars will be used and they are ok.