Affects Version/s: None
Fix Version/s: 1.0.0-beta-2
The file conf/logging.properties in CATALINA_BASE has a special meaning during Tomcat startup:
its precence leads to Tomcat using JULI-Logging with conf/logging.properties as the configuration.
Case 1: User removed Tomcat standard conf/logging.properties after Tomcat installation as part of the procedure usually used to let Tomcat log via log4j.
If there is no conf/logging.properties the openejb installer for Tomcat produces such a file.
During the next restart Tomcat detects that file and by the logic in catalina.sh it will then switch automatically to JULI-Loggin for its own purposes. It will try to configure JULI via conf/logging.properties, but the syntax of that file if for log4j, not juli. So Tomcat logging will be broken.
Case 2: conf/logging.properties coming from the Tomcat installation exists.
(not tested) openejb will add its own log configuration lines (because in the standard Tomcat file there are no openejb entries) and will thus produce a file with some statements for JULI, and some for log4j, making it unusable for both logging frameworks.
Choosing the name conf/logging.properties was unfortunate, because that file already had a special incompatible meaning for Tomcat. It seems you should either choose a different file name or a different directory.
|Status||Open [ 1 ]||Closed [ 6 ]|
|Fix Version/s||1.0.0-beta-2 [ 12318446 ]|
|Resolution||Fixed [ 1 ]|
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|1059d 59m||1||Romain Manni-Bucau||09/Oct/11 22:00|