[
https://issues.apache.org/jira/browse/GERONIMO-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606021#action_12606021
]
David Jencks commented on GERONIMO-4104:
----------------------------------------
See
http://cwiki.apache.org/GMOxDOC21/configuring-application-specific-logging-with-log4j.html
for guidelines about how to set up app logging so as to be configurable yet
not interfere with geronimo's logging.
> Tomcat logging is broken
> ------------------------
>
> Key: GERONIMO-4104
> URL: https://issues.apache.org/jira/browse/GERONIMO-4104
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Tomcat
> Affects Versions: 2.1.1
> Reporter: Kevan Miller
> Assignee: Jarek Gawor
> Priority: Critical
> Fix For: 2.1.2
>
>
> Tomcat logging seems to be broken. When deployment errors occur, the root
> causes aren't being logged. This makes problems hard to diagnose.
> I suspect that the problem is being caused by Tomcat's use of Log4JLogger
> from juli-adapters:
> repository/org/apache/tomcat/extras/juli-adapters/6.0.16/juli-adapters-6.0.16.jar
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
