geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Gawor (JIRA)" <>
Subject [jira] Commented: (GERONIMO-4104) Tomcat logging is broken
Date Wed, 18 Jun 2008 04:12:45 GMT


Jarek Gawor commented on GERONIMO-4104:

I do not see any problem with Tomcat logging in general. However, I do see a problem when
JSPWiki is deployed. JSPWiki is reconfiguring the global log4j settings (the root logger)
using its own configuration file (log4j settings are specified in the WEB-INF/
file). By default, JSPWiki sets up logging to /tmp/jspwiki.log file and that's where the actual
root exceptions are logged to. To disable JSPWiki from reconfiguring the root logger one needs
to comment out the following line in the file:


After commenting out that line in the file, the full exceptions were logged
to geronimo.log file.

> Tomcat logging is broken
> ------------------------
>                 Key: GERONIMO-4104
>                 URL:
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Tomcat
>    Affects Versions: 2.1.1
>            Reporter: Kevan Miller
>            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.

View raw message