Hi, to complete the picture, attached is the configuration we use.
Carsten > -----Original Message----- > From: Carsten Ziegeler [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 18, 2004 2:31 PM > To: 'Turbine JCS Developers List' > Subject: RE: Store surviving a shutdown > > Hi Aaron, > > yes we are running the latest version from CVS and yes we get > the two files and they are both not empty. > > But on startup the files are overwritten. Is there any > configuration for this perhaps? > > Carsten > > > -----Original Message----- > > From: Aaron Smuts [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, May 18, 2004 2:25 PM > > To: 'Turbine JCS Developers List' > > Subject: RE: Store surviving a shutdown > > > > The latest jcs version if shutdown properly, should write two files > > per region. One called keys the other data. One startup it should > > read the keys into memory and everything in the data folder > should be > > available just as before shutdown. > > > > You need to make sure that the elements in the regions are not > > expiring also. > > > > Are you getting the two files? If not, did you build the latest > > version of jcs from source? > > > > Cheers, > > > > Aaron > > > > > > > -----Original Message----- > > > From: Carsten Ziegeler [mailto:[EMAIL PROTECTED] > > > Sent: Tuesday, May 18, 2004 5:36 AM > > > To: 'Turbine JCS Developers List' > > > Subject: RE: Store surviving a shutdown > > > > > > Just an additional info: > > > It seems that the files are written properly on shutdown, but on > > > startup they are overwritten with empty files. > > > > > > Carsten > > > > > > > -----Original Message----- > > > > From: Upayavira [mailto:[EMAIL PROTECTED] > > > > Sent: Tuesday, May 18, 2004 9:46 AM > > > > To: [EMAIL PROTECTED] > > > > Subject: Store surviving a shutdown > > > > > > > > Hello, another Cocooner popping in for a visit! > > > > > > > > In our explorations of JCS, one thing I believe that was > > said about > > > > it is that the store doesn't persist through a shutdown. > > > > > > > > Now, the current (slightly buggy) implemention within > > Cocoon does. > > > > Is there any way to make it persists through a restart, > > or to make > > > > it configurable? > > > > > > > > The main usecase for Cocoon is running within a servlet, where > > > > arguably surviving a shutdown isn't crucial. However, > > Cocoon can be > > > > used from the command line to statically generate web > sites. For > > > > this, a working persistent cache that survives shutdown can be > > > > invaluable. Each time you run it, it can check to see > > whether a page > > > > in the cache is up-to-date, and if so, not bother > generating the > > > > page. This should be able to offer a great performance > > improvement > > > > (but didn't because our previous implementation of a persistent > > > > store was slow). So you'd make me a happy man if you gave me a > > > > responsive persistent store that could survive a shutdown. > > > > > > > > Regards, Upayavira > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: > > [EMAIL PROTECTED] > > > > For additional commands, e-mail: > > > > [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: > > [EMAIL PROTECTED] > > > For additional commands, e-mail: > > [EMAIL PROTECTED] > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > [EMAIL PROTECTED] > > For additional commands, e-mail: > > [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
