I can confirm that removing commons-logging.jar (and commons-logging-api.jar) from the ear makes the problem go away. I just experienced the same issue when moving an ear that worked fine under 3.2.3 to JBoss 3.2.4.
You may be referencing commons-logging from within your ear without knowing it - many jakarta distributions use it under the covers. The commons-logging.jar is distributed under the jboss/lib directory - my theory (i.e. wild-ass guess) is that something in 3.2.4 is using commons-logging now - perhaps a piece of tomcat 5 - in a different way and gumming up the deployments. There doesn't seem to be any downside to removing commons-logging from my ear - all my log statements (even those that use commons instead of log4j directly) seem to be working properly. Can anyone confirm this behavior in the JBoss 4 beta? Any guess if this will be a stable feature. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3839648#3839648 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3839648 ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
