The first few lines of log4j.properties should help: # This is the configuring for logging displayed in the Application Server log4j.rootCategory=INFO, stdout
# Replace the line above if you want to put a log file into the directory # you start Tomcat from # log4j.rootCategory=INFO, stdout, R Matt On 5/14/07, rfisk <[EMAIL PROTECTED]> wrote:
In 1.9.4 there is a log4j properties in WEB-INF/classes which attempts to stream output for the context into its own log file: [EMAIL PROTECTED]@.log The problem is that even after the build replaces @APPNAME@ with the proper context, the logfile <CONTEXT>.log is never created. All output ends up in catalina.out. Is there something else I'm missing in tomcat config that allows this to occur properly? It's busted both in my sandbox and live deployment. -- View this message in context: http://www.nabble.com/Bug-in-1.9.4-log4j-settings--tf3753805s2369.html#a10608447 Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- http://raibledesigns.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
