Mailing-List: contact turbine-jcs-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Turbine JCS Users List" <turbine-jcs-user@jakarta.apache.org>
From: Christian Kreutzfeldt <christian.kreutzfeldt@gmx.de>
Organization: iCS
To: "Turbine JCS Users List" <turbine-jcs-user@jakarta.apache.org>
Subject: Re: Indexed Disk Cache Configuration
Date: Thu, 15 Jan 2004 08:55:54 +0100
User-Agent: KMail/1.5.2
References: 
 <OFE97619B3.4DC5353A-ONCA256E1C.00234F39-CA256E1C.00238CF4@nm.com.au>
In-Reply-To: 
 <OFE97619B3.4DC5353A-ONCA256E1C.00234F39-CA256E1C.00238CF4@nm.com.au>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200401150855.54877.christian.kreutzfeldt@gmx.de>

On Thursday 15 January 2004 07:28, ankur.kumar@axa.com.au wrote:
Hi!

>> All of the keys are kept in memory in JCS.  That is why the keys file
>> remains at 0.
> As per the source code of IndexedDiskCache, keys can also be saved and
> retrieved to disk and not necessarily be maintained in memory.
Yeah, I encountered that problem a while ago too when we tried to use the
JCS caching system for a load balanced website. 
According to some people on this list, the key and the data file should be 
written at shutdown. Unfortunately, the key file cannot be written since the
flag which indicates that the software performs a shutdown is questioned
before writing the file. Since the flag has been set to false before and the
check is on "equals true" the code which stores the keys cannot be executed.
A time ago I posted a fix but never got any feedback.


Christian


---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-jcs-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-jcs-user-help@jakarta.apache.org