[
https://issues.apache.org/jira/browse/FOR-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535887
]
Thorsten Scherler commented on FOR-1049:
----------------------------------------
The real problem lies in the web.xml (here forrest).
We use here:
...
<!--
Set commons-logging classes, in particular JCS, to use the logkit so the
log messages
are properly handled by cocoon.
-->
<init-param>
<param-name>force-property</param-name>
<param-value>
org.apache.commons.logging.Log=org.apache.commons.logging.impl.LogKitLogger
</param-value>
</init-param>
<!--
This parameter allows you to startup Cocoon2 immediately after startup
of your servlet engine.
-->
<load-on-startup>1</load-on-startup>
...
This combination is forcing the usage of the LogKitLogger for ALL servlets in
your servlet container. I tested with Jetty as well and you will get the same
error.
The explanation is that since the cocoon servlet is loaded first we are setting
the org.apache.commons.logging.Log variable for the whole container.
http://commons.apache.org/logging/troubleshooting.html#Fixes
Meaning no other servlet can override this any more, very bad if you have
different servlets/contexts.
The solution is instead of using an init-param a context-param. This way every
context can handle its on logging:
...
<context-param>
<param-name>force-property</param-name>
<param-value>
org.apache.commons.logging.Log=org.apache.commons.logging.impl.LogKitLogger
</param-value>
</context-param>
...
Will apply a fix ASAP.
> Forrest war is crashing apache-tomcat-5.5.23 upon restart
> ---------------------------------------------------------
>
> Key: FOR-1049
> URL: https://issues.apache.org/jira/browse/FOR-1049
> Project: Forrest
> Issue Type: Bug
> Components: Launch servlet WAR
> Reporter: Thorsten Scherler
> Priority: Critical
>
> http://www.mail-archive.com/[EMAIL PROTECTED]/msg00779.html
> "I'm having some problems with the present svn head (two days old): the war
> it creates installes fine in Tomcat when deployed through Tomcat's HTML
> Manager, and as long as Tomcat is running without interruption, there's no
> problem. But when restarted, Tomcat crashes severely. This happens only when
> the Forrest war is installed, without the Forrest war, there is no problem.
> Config:
> - (almost) latest Forrest svn
> - Tomcat 5.5.9
> - Java 1.5_02
> - Win2k server"
> I am seeing the same issue on an ubuntu linux.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
