-
1. Re: never expiring cache in JBoss Data Virtualization
Use a negative ttl to indicate no expiration.
-
2. Re: never expiring cache in JBoss Data Virtualization
Still I see the cache invalidates after say more than 60 mis. I think this is due to the default expiry in VDB system. Could you please suggest on how to get thru this.
-
3. Re: never expiring cache in JBoss Data Virtualization
Can you elaborate on default VDB expiry? Which values u are referring to? If the VDB is undeployed the cache is removed.
-
4. Re: never expiring cache in JBoss Data Virtualization
Thanks, I would like to know which parameter controls the default VDB expriy? kindly help.
-
5. Re: never expiring cache in JBoss Data Virtualization
Ok, there is none. The cache defaults to VDB scope (look at "scope" attribute in CacheHint), that means for the life of the VDB deploy/undeploy cycle or server re-starts. If you are seeing the behavior otherwise, then I am not sure why the anomaly.
Ramesh..
-
6. Re: never expiring cache in JBoss Data Virtualization
If a negative ttl is specified in the cache hint it will trump all other ttl settings - either at the Infinispan level or via an extension property on objects/models involved. You will want to make sure through the log or other investigations that the entry is expiring because of ttl and not for another reason, such as being pushed out of the cache by other entries.