cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hans Ulrich Niedermann <>
Subject Re: [C2] SitemapManager.class change or bug ?
Date Thu, 05 Oct 2000 17:55:21 GMT
Marcus Crafter <> writes:

> java.lang.NullPointerException
>         at org.apache.cocoon.sitemap.Handler.process(
>         at org.apache.cocoon.sitemap.Manager.invoke(
>         at org.apache.cocoon.Cocoon.process(
>         at org.apache.cocoon.servlet.CocoonServlet.service(
>         at javax.servlet.http.HttpServlet.service(
>         at org.apache.tomcat.core.ServletWrapper.doService(
>         at org.apache.tomcat.core.Handler.service(
>         at org.apache.tomcat.core.ServletWrapper.service(
>         at org.apache.tomcat.core.ContextManager.internalService(
>         at org.apache.tomcat.core.ContextManager.service(
>         at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(
>         at org.apache.tomcat.service.TcpWorkerThread.runIt(
>         at org.apache.tomcat.util.ThreadPool$
>         at

I never got C2 to work with Tomcat 3.1 within the last 2 months. I
always got the same stack trace. It is a result from a
java.lang.VerifyError within the thread that asynchronously recreates
the sitemap. (You probably don't see the VerifyError any more because
the system.out logging code seems to have been removed. I haven't
actually checked this, though.)

But I finally managed to get Tomcat 4.0 to work properly (the trick is
to check out the correct jakarta-servletapi branch) and C2 works with
it like a charm.

BTW, a step by step HOWTO for installing Cocoon 2 and Tomcat 4.0 is
available from


if anyone is interested in it.


View raw message