[
https://issues.apache.org/jira/browse/TOMEE-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Blevins moved OPENEJB-957 to TOMEE-11:
--------------------------------------------
Component/s: (was: tomee)
Affects Version/s: (was: 3.1)
Key: TOMEE-11 (was: OPENEJB-957)
Project: TomEE (was: OpenEJB)
> conf/logging.properties conflicts with juli configuration for Tomcat
> --------------------------------------------------------------------
>
> Key: TOMEE-11
> URL: https://issues.apache.org/jira/browse/TOMEE-11
> Project: TomEE
> Issue Type: Bug
> Environment: All
> Reporter: Rainer Jung
> Priority: Minor
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
