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 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3949868#3949868 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3949868 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
