Hi Martin, Just a stupid question, is the log4j.properties file correctly set?
Regards, Thomas ---------- Initial Header ----------- From : "Martin Lidgard" <[EMAIL PROTECTED]> To : "'Turbine Users List'" <[email protected]> Cc : Date : Fri, 8 Dec 2006 10:04:18 +0100 Subject : Turbine 2.3.0/Commons-Logging configuration under Tomcat 5.5 Hello, I am working on upgrading our hosting environment from Tomcat 4.1 to Tomcat 5.5. In our current Tomcat 4.1 environment we are running Turbine 2.3 (2.3.0, not 2.3.2) with commons-logging-1.0.4 and log4j-1.2.8 using more or less the default logging configuration from Turbine. When upgrading to Tomcat 5.5 the logging does not work as intended. Logging is written to the webapp's local log as expected during startup, with logging level DEBUG for the log4j.logger.myapp entry: myapp.log (22817 bytes) scheduler.log (127 bytes) torque.log (0 bytes) turbine.log (0 bytes) velocity.log (0 bytes) Initialization logging is written to /var/log/tomcat/catalina.out, showing among other things an init of Log4j: [...] log4j: Parsing for [root] with value=[DEBUG, console, myapp]. log4j: Level token is [DEBUG]. log4j: Category root set to DEBUG log4j: Parsing appender named "console". log4j: Parsing layout options for "console". log4j: Setting property [conversionPattern] to [%-5r %-5p %-25.25c{1} - %m%n]. log4j: End of parsing for "console". log4j: Setting property [threshold] to [DEBUG]. log4j: Parsed "console" options. log4j: Parsing appender named "myapp". log4j: Parsing layout options for "myapp". log4j: Setting property [conversionPattern] to [%d %-5p %c{1} - %m%n]. log4j: End of parsing for "myapp". log4j: Setting property [append] to [true]. log4j: Setting property [file] to [/usr/local/tomcat/webapps/myapp//logs/myapp.log]. log4j: Setting property [threshold] to [DEBUG]. log4j: setFile called: /usr/local/tomcat/webapps/myapp//logs/myapp.log, true log4j: setFile ended log4j: Parsed "myapp" options. [...] After a number of lines of log messages in catalina.out describing initialization of Turbine services, there seems to be a second Log4j initialization using the same configuration as above. After this, debug messages that are specific to the initialization of "myapp" are written to both catalina.out and webapps/myapp/logs/myapp.log, as expected. However, when performing the first request to the servlet, no further debug logging is written to either catalina.out or myapp.log. Only INFO-level logging is written to catalina.out describing the late initialization of the Turbine services. Is Log4j reconfigured somehow during the request without telling? Could there be a link missing between Tomcat's request and the logging? Any ideas or sample configurations would be greatly appreciated. Thanks, Martin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------- ALICE SECURITE ENFANTS --------------------- Protégez vos enfants des dangers d'Internet en installant Sécurité Enfants, le contrôle parental d'Alice. http://www.aliceadsl.fr/securitepc/default_copa.asp --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
