i ran into this last night. it's because you are including a log4j.jar in your ear that's older than the one in /lib.
the problem is that your old log4j.jar is using the new log4j.xml configuration from /conf. so to fix this you need to do one of the following in order of preference: 1. remove log4j.jar from your ear so your app ends up using the most recent one from /lib which is in sync with the /conf/log4j.xml 2. add log4j.xml to your ear but then you'll have to add the log4j service mbean to some jboss-service.xml in your ear. <a href="http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3826561#3826561";>View the original post</a> <a href="http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3826561>Reply to the post</a> ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
