Today I tried to deploy my webapp onto JBoss app server and stumbled upon this error/bug/issue :(
It appears that JBoss is the first one who gets to configure Log4j configuration and if you try to configure it somehow later, the Log4j goes crazy and the app cannot be deployed.
Well, what else could I do? I had to turn of Log4j configuration (I was using Spring’s org.springframework.web.util.Log4jConfigListener for this purpose) for the time being.
As far as I’m concerned JBoss’s log4j configuration is managed through an xml config located in conf/jboss-log4j.xml, which is the place where one can configure his application’s logging.
First published on the old anydoby.com blog on 2007-07-07.