yes, there are some cache issues with Manakin 1.1 on DSpace 1.4.2, somewhere way back in the email archive for dspace-dev there is a patch that fixes the issue... Or alternatively you could update to DSpace 1.5.0 or 1.5.1... And finally if it's not going to cause problems you can just turn off caching in cocoon:

Open, webapp/sitemap.xmap, and locate the following lines (around line 168ish)

<map:pipes default="caching">
<map:pipe name="noncaching" src="org.apache.cocoon.components.pipeline.impl.NonCachingProcessingPipeline">
<map:pipe name="caching" src="org.apache.cocoon.components.pipeline.impl.CachingProcessingPipeline">

Change the default attribute to = 'noncaching' this will turn off catching for all pipelines.


On Jan 29, 2009, at 12:26 PM, Rafael Henkin wrote:

            We have been experiencing some problems with the Cocoon cache. Sometimes it keeps growing undefinedly. While itís something that doesnít occur everyday, when it happens we must restart Tomcat or the FS will have no space left. We have also noticed that sometimes the cache is apparently not used at all.
            In cocoon.xconf the transient-store (which from what I read defines the Cocoon cache) is set to 10000, along with the normal store. I would like to know if anyone has any advice regarding this?
            Rafael Henkin
This email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
DSpace-tech mailing list