Jboss comes with log4j and uses it for the logging of the jboss server.
This means that the log4j.jar is the one loaded by jboss and the configuration file is the one loaded by jboss. You can find the log4j.xml (or log4j.properties for older versions of jboss) file in the configuration directory of the jboss server. You can modify this file to specify where the log entries go.
You will probably find your log entries in the jboss log file for now.
What if this is not a valid solution?
Has anyone done work on allowing servetl webapplication to use there own log4j instances to log?
The reason I ask is I have serveral webapps that run in tomcat right now. They work great and do there own logging. If I want to move them to jboss I want them to work EXACLTY like they do today. (That is copy a single war file and 100% of everything including logging is taken care of)
But because jboss is not loading log4j in it own classloader it and webapps in there own (like Tomcat does) it is causing an issue. Ideas?