cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 26709] - cocoon 2.0.4 and Tomcat 5.0.16
Date Sun, 15 Feb 2004 00:53:56 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26709>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26709

cocoon 2.0.4 and Tomcat 5.0.16

afroehli@student.uni-kassel.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|DUPLICATE                   |



------- Additional Comments From afroehli@student.uni-kassel.de  2004-02-15 00:53 -------
Hi, I got exactly the same message when I tried to deploy cocoon. I then 
recompressed the batik file as described in bug#26392-section and Tomcat is 
able to start cocoon now, BUT ... when I try to access cocoon I get the 
following message now:

>Cocoon 2 - Internal servlet error
>
>-----------------------------------------------------------------------------
>type fatal
>
>message Cocoon was not initialized.
>
>description Cocoon was not initialized. Cannot process request.
>
>sender org.apache.cocoon.servlet.CocoonServlet
>
>source Cocoon servlet
>
>request-uri
>
>/cocoon/

I also followed the link and tried using the newer batik-all-1.5.jar, that was 
suggested in the bug#26709-section too, but it has the same effect - Tomcat 
has no problems anymore but Cocoon is not running.

That's why I reopen this bug.

Can someone maybe just post their running configuration as long as there is no 
solution to this problem?

Mime
View raw message