I'm certainly no expert on JCS, but I am successfully using it (sort of) with Hibernate 2.0.
The "DC" is supposed to reference another cache configuration (which is typically a Disk Cache -- hence the DC). The full cache configuration at the beginning of your post includes a commented-out definition of a disk cache (jcs.auxiliary.DC). You don't have one defined, so that's why you see the "ERROR" when you start-up.
Hibernate creates a different JCS region for each <jcs-cache> tag you have in your mapping file. The cache names are the fully qualified name of the class for class-level caching. For caching of properties (one-to-many or many-to-many collections), the cache name is the fully qualified name of the class containing the property with ".<property_name>" appended. So you could configure each JCS cache that hibernate will use individually.
The "jcs.default" cache configuration is used as the configuration for any region that is not explicitly provide a cache configuration. The cache configuration at the beginning of your posting defines cache configurations for three regions -- Country, Region, CreditCard -- plus the default "jcs.default" to be used for any other regions.
MaxObjects indicates the maximum number of objects that can exist within a region configured by those properties. Your understanding of MaxLifeSeconds and IdleTime is correct. I'm not sure what IsEternal, isSpool, IsRemote and IsLateral do, but I don't have any them defined in my cache configuration and things work fine. I'd assume that IsRemote/IsLateral have to do with whether you're using a remote cache or a lateral cache (which in your example, you aren't because you are using a memory cache).
Just so you know, JCS's LRUMemoryCache causes memory leaks. There's a post on this forum that discusses the problems in detail. . . search for Topic "JCS IndexedDiskCache deadlock/LRUMemoryCache memory leak" from October 2003. Since we actually want our cached objects to have an infinite life, we wrote our own Cache class that extends JCS's AbstractMemoryCache class and is just a wrapper around HashMap.
There also seems to be a problem with JCS starting a Thread associated with each region that is created. The Thread seems to just block and do nothing, but it's still weird.
Hope this helps.
Sarah
Login
FAQ
Search
