Jann Forrer wrote:
Jörn Nettingsmeier wrote:
Jann Forrer wrote:
Richard Frovarp wrote:
Jörn Nettingsmeier wrote:
Richard Frovarp wrote:
Jörn Nettingsmeier wrote:
Richard Frovarp wrote:
I am getting the following error:
cocoon-ehcache-1Cache: Could not remove disk store entry for
PK_G-file-file:/usr/local/lenya-1.4.x/build/lenya/webapp/lenya/pubs/demo/config/publication.xconf_T-xslt-file:/usr/local/lenya-1.4.x/build/lenya/webapp/lenya/xslt/modules/modules2xinclude.xsl;area=authoring_T-xinclude-XInclude.
Error was cocoon-ehcache-1 Cache: The Disk store is not active.
i've seen a similar error twice during the last 2 days.
but mine is transitional - when i reload the page, it usually goes
away.
looks like a cocoon issue to me, but i have no time to investigate
atm.
one way to pinpoint the problem could be to check the cocoon svn
logs for changes to the caching mechanism and then to revert only
the cocoon external branch to before that change...
I've found the error, not sure why I just began seeing the problem,
however. On my install there is a /tmp/cocoon-ehcache-1.data and a
/tmp/cocoon-ehcache-1.index. I have been trying to run two versions
of Lenya at once on the machine. One for my users to test on, one for
me to test different things, that may or may not require restarting
Lenya. Depending on which user owns the cache files, the other users
have issues. Next step is figuring out if there is a way to get my
two installs to use different directories.
ah, yes. that was probably my mistake as well... thanks for this info!
i wonder if it should be documented soomewhere, but i can think of a
good place. if you do figure out how to run multiple lenya/jetty
instances concurrently on one machine, perhaps you could create a
short wiki page?
regards,
jörn
Here is what I've found. If I download Cocoon 2.1.9 and run it as a test
application, it will dump the cache files in
Jetty__8888__/cocoon-files/cache-dir. If I grab the latest snapshot,
that directory exists, but the cache files are not in that directory.
Since that directory obviously has the port in its name, running
multiple copies in the past would not have been an issue. Now the files
follow the java.io.tmpdir property. If you change this property, you can
get it to put the cache files in different locations.
The ehcache can be configured in a file called ehcache.xml. You can find
this file in your cocoon dir e.g.
./cocoon-2.1.X/src/java/org/apache/cocoon/components/store/impl/ehcache.xml
Within this file you can (among other things) set the diskStore path
(defaul is: <diskStore path="java.io.tmpdir"/>).
BTW, i would recommend to change the entries for productive use anyway.
the <defaultCache> too. By default eternal is set to true which lead
to quite big cache files for our installation.
Sorry, a really bad sentence!
good point. we need a production howto when 1.4 gets out... i'm starting
a wiki page. could you add some caching information?
Yes, I can add a possible configuration for the ehcache there.
thanks. hack away, everybody:
http://wiki.apache.org/lenya/How_to_tune_Lenya_1%2e4_for_Production_Use
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
