You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by bu...@apache.org on 2004/07/13 19:48:32 UTC

DO NOT REPLY [Bug 30084] New: - JCS cache errors

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=30084>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=30084

JCS cache errors

           Summary: JCS cache errors
           Product: Cocoon 2
           Version: Current CVS 2.1
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: core
        AssignedTo: dev@cocoon.apache.org
        ReportedBy: cheche@che-che.com


Hi.
We are getting strange errors related to JCS within forrest.
GRAVE: Failure updating element, cacheName: main, key:
PK_G-file-cocoon://samples/menulinks-ihtml-sample.html?pipelinehash=-1429098877448307785_T-xslt-file:/home/cheche/xml/forrest/trunk/src/core/bin/../context/resources/stylesheets/site2book.xsl
java.lang.InterruptedException
        at java.lang.Object.wait(Native Method)
        at
org.apache.jcs.utils.locking.ReadWriteLock.writeLock(ReadWriteLock.java:127)
        at
org.apache.jcs.auxiliary.disk.indexed.IndexedDiskCache.doUpdate(IndexedDiskCache.java:252)
        at
org.apache.jcs.auxiliary.disk.AbstractDiskCache$MyCacheListener.handlePut(AbstractDiskCache.java:417)
        at
org.apache.jcs.engine.CacheEventQueue$PutEvent.doRun(CacheEventQueue.java:440)
        at
org.apache.jcs.engine.CacheEventQueue$AbstractCacheEvent.run(CacheEventQueue.java:358)
        at
org.apache.jcs.engine.CacheEventQueue$QProcessor.run(CacheEventQueue.java:327)


Before open a bug with cocoon, I tried to replace JCS with todays version from:
http://cvs.apache.org/viewcvs.cgi/jakarta-turbine-jcs/tempbuild/#dirlist

This seems to fix our issues. So I guess that the problem has been fixed upstream. 

I guess that upgrade to this version seems wise for my point of view..

Cheers,
Cheche