It does appear that there is an older version of Log4J hanging around. Do two things:

1) Post the results from entering: $JAVA_HOME/bin/java

2) Change the OPTS env var in run.conf, adding the option '-verbose:class'. Then start the app server again, redirecting the output to a file (you will get a lot of output). Then grep the file for 'log4j'. This should tell you which JAR file the log4j classes are in. When I did this, I saw (among many other lines of grep results):

[Loaded org.apache.log4j.spi.AppenderAttachable from file:/opt/jboss-4.2.0.GA/lib/log4j-boot.jar]
[Loaded org.apache.log4j.Category from file:/opt/jboss-4.2.0.GA/lib/log4j-boot.jar]
[Loaded org.apache.log4j.Logger from file:/opt/jboss-4.2.0.GA/lib/log4j-boot.jar]
[Loaded org.apache.log4j.Priority from file:/opt/jboss-4.2.0.GA/lib/log4j-boot.jar]
[Loaded org.apache.log4j.Level from file:/opt/jboss-4.2.0.GA/lib/log4j-boot.jar]
[Loaded org.apache.log4j.LogManager from file:/opt/jboss-4.2.0.GA/lib/log4j-boot.jar]


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4071276#4071276

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4071276
_______________________________________________
jboss-user mailing list
jboss-user@(protected)
https://lists.jboss.org/mailman/listinfo/jboss-user