Rename conf/log4j.xml to conf/jboss-log4j.xml to allow log4j.properties override. --------------------------------------------------------------------------------- Key: JBAS-1853 URL: http://jira.jboss.com/jira/browse/JBAS-1853 Project: JBoss Application Server Issue Type: Task Security Level: Public(Everyone can see) Components: Logging Affects Versions: JBossAS-4.0.2 Final Reporter: Scott M Stark Fix For: JBossAS-4.2.0.CR1 The default logging configuration location mechanism of log4j will find the server conf/log4j.xml file. One simple isolation step is to rename this file conf/jboss-log4j.xml since we do not rely on the default logging configuration location mechanism of log4j. The next level of isolation is to actually create a unique LoggerRepository for use by the jboss Logger in the Log4jService. The concern is that components like jgroups, hibernate, tomcat, etc. using commons logging will fail to pickup the Log4jService LoggerRepository. We probably need to configure commons logging as well from the Log4jService with a flag that can disable this.