[jira] Resolved: (GERONIMO-4104) Tomcat logging is broken

["Jarek Gawor (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GERONIMO-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jarek Gawor resolved GERONIMO-4104.
-----------------------------------

    Resolution: Invalid
      Assignee: Jarek Gawor

I'm closing the bug as I don't think there is much we can do if the application chooses to reconfigure the log4j settings. 


> 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.