Thank you Mavin. Removing log4.properties and commenting out Log4jConfigListener in web.xml did the trick.
BTW, for those using Tomcat, if you have the log4j JAR and dependencies plus a log4j.xml in the Tomcat lib folder... you get the same centralized log4j behavior as you do in jBoss. It sure beats having to configure log4j for each app! -----Original Message----- From: Marvin Addison [mailto:[email protected]] Sent: Thursday, July 16, 2009 12:46 PM To: [email protected] Subject: Re: [cas-user] cas.log location > Would CAS have a problem if we remove the CAS-provided log4j.properties file > and rely on the one from Tomcat/jBoss? The answer depends on *how* CAS > reads its log4j properties. CAS uses the Spring Log4jConfigListener to load its configuration. The web.xml that ships with CAS has a comment that says to disable that listener on JBoss. Did you do that? If so, CAS should be able to get the a logger instance from the JBoss container's logger repository and it will use the configuration defined in the jboss-log4j.xml file JBoss deployers know and love. We have deployed CAS on both JBoss (4.0.2 IIRC) and Tomcat 5.5+6.0 and have had no problem configuring logging to suit our needs on either platform. M -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
