portals-jetspeed-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sie, Yang" <yang....@fmr.com>
Subject RE: Preload OJB Persistent Layer at App Server Startup
Date Thu, 01 Nov 2007 13:04:39 GMT

Thank you for your reply. I am ok with the utilizing Prefs. API part of
it, let me think more on that. As far as where to run it, for discussion
purpose and simply because we are using DBPageManager, I am thinking,
from Jetspeed's point of view, to put it somewhere in the
DatabasePageManagerCache. It there all cache got instantiated? Then what
about for people using file system PageManager?

Thank you,


>-----Original Message-----
>From: David Sean Taylor [mailto:david@bluesunrise.com] 
>Sent: Wednesday, October 31, 2007 5:50 PM
>To: Jetspeed Users List
>Subject: Re: Preload OJB Persistent Layer at App Server Startup
>On Oct 31, 2007, at 11:42 AM, David Sean Taylor wrote:
>> On Oct 31, 2007, at 11:00 AM, Keshavan, Rango wrote:
>>> One of the issues with this is that we would also have to never  
>>> timeout
>>> the pref cache, as when the cache is timed out, we have the  
>>> performance
>>> issue again of reading the preference cache...
>>> David, do you see any issues with that?
>> You would have to tweak the preferencesCache to never expire, here  
>> are the default settings  in ehcache.xml
>>     <cache name="preferencesCache"
>>            maxElementsInMemory="10000"
>>            maxElementsOnDisk="1000"
>>            eternal="false"
>>            overflowToDisk="false"
>>            timeToIdleSeconds="28800"
>>            timeToLiveSeconds="28800"
>>            memoryStoreEvictionPolicy="LFU">
>meant to set this to true:
>If eternal,  timeouts are ignored and the element
>                           is never expired.

To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org

View raw message