Christopher Watson wrote:

>Could anyone help with this cache problem ...
>
>I seem to get these errors creep into existence for certain static document
>(e. g. images).
>Everything is fine for a couple of days, then I start getting cache errors
>on access to some static files.
>Once a certain URI starts failing, it keeps failing, then gradually others
>join in.
>To restore access to them, I have to stop tomcat, delete the work directory
>(which includes the cache of course!) and restart tomcat.
>Then everything is fine for a couple of days again.
>
>I've checked the recommendations for heapsize and freememory as far as I
>understand them.
>
>I've done a search of the mailing list, but have not managed to find
>anything specific to this error.
>
>System is Windows 2000 IIS5 using ISAPI to tomcat 4.0.1 to cocoon 2.0.1
>jdk1.3.1
>
>Here's the error I get.
>
>
>(By the way, /main/ is the name of my cocoon context and directory)
>  
>
...

>java.lang.ClassCastException: org.apache.cocoon.caching.CachedEventObject
>       at
>org.apache.cocoon.components.pipeline.CachingStreamPipeline.processReader(Ca
>chingStreamPipeline.java:154)
>       at
>org.apache.cocoon.components.pipeline.AbstractStreamPipeline.process(Abstrac
>tStreamPipeline.java:125)
>       at
>org.apache.cocoon.components.pipeline.CachingStreamPipeline.process(CachingS
>treamPipeline.java:249)
>

This looks like clash in cache: object of unexpected type was returned 
to the pipeline.

Try upgrading to the 2.0.3 version and tell us your experience.

If this is not the option, I can recommend adding another instance of 
the cache (with different role) and patching CachingStreamPipeline to 
use this another store. Then should be no clashes like this.

Vadim



---------------------------------------------------------------------
Please check that your question  has not already been answered in the
FAQ before posting.     <http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail:     <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>

Reply via email to