cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Berin Loritsch <>
Subject Re: [c2] the dreaded arrayindexoutofbounds exception returns
Date Thu, 10 May 2001 21:18:19 GMT
Donald Ball wrote:
> org.apache.cocoon.ProcessingException: Failed to execute
> pipeline.:java.lang.IndexOutOfBoundsException: Index: -1, Size: 0
>         at
> org.apache.cocoon.components.pipeline.CachingEventPipeline.process(
>         at
> org.apache.cocoon.components.pipeline.CachingStreamPipeline.process(
>         at
> org.apache.cocoon.www.sitemap_xmap.process(
>         at
> org.apache.cocoon.www.sitemap_xmap.process(
>         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(
> i just got this after leaving my c2 webapp alone for many hours. a tomcat
> restart later and it's back to normal. what gives? this is for sure a show
> stopper bug. :)

Hopefully I fixed this.  JaxpParser is no longer Poolable or Recyclable and
is SingleThreaded.  The reason being is that Xerces told us (on their site)
that you can't use a parser twice.  It is subject to race conditions, and if
it is used again before it is done cleaning itself up, we will get the
dreaded IndexOutOfBoundsException.

This is the only way I know of to handle this issue--short of hacking Xerces
code to allow a Parser to be reused.

To unsubscribe, e-mail:
For additional commands, email:

View raw message