At the moment logging is done via the built-in JULI lib, which is modified by Tomcat to use app specific class loader config. The logging.properties file is embedded into the war file, and at first glance this appears to be make it difficult to change the logging configuration without re-compiling, repackaging, and redeploying a new version of the app. Ideally we can simply modify the global Tomcat conf/logging.properties and restart Tomcat for changes to take effect. At the moment changes to the global file appear to be overridden by the app specific config.
Note: At runtime I believe JConsole can connect to Tomcat via RMI and modify log level via MBeans, but modifying a config file and restart may be simpler.
At the moment logging is done via the built-in JULI lib, which is modified by Tomcat to use app specific class loader config. The logging.properties file is embedded into the war file, and at first glance this appears to be make it difficult to change the logging configuration without re-compiling, repackaging, and redeploying a new version of the app. Ideally we can simply modify the global Tomcat conf/logging.properties and restart Tomcat for changes to take effect. At the moment changes to the global file appear to be overridden by the app specific config.
Note: At runtime I believe JConsole can connect to Tomcat via RMI and modify log level via MBeans, but modifying a config file and restart may be simpler.