You first enable JGroups in oscache.properties per OSCache docs:
http://www.opensymphony.com/oscache/wiki/Clustering.html
And then in your postUpdate/postRemove/postPersist listener you call
dataContext.getQueryCache().removeGroup("groupName");
"groupName" should be the same String you are u
Thanks for that information I will give it ago. Do you have an example of a
listener which performs a flush. This is really what I am after, as there
are a relatively small tables which need to be synched, others don't need to
be.
regards Malcolm Edgar
On Wed, Sep 23, 2009 at 11:51 PM, Andrus Ad
You are correct - flushing query cache groups across the cluster with
JGroups (or something else) is a low overhead way to propagate
updates. My usual setup is to have post-update/remove/persist
listeners generate a distributed event with a cache group appropriate
for the object being saved
Hi All,
I am looking to improve the performance of a set of web applications
running. We have one application which is used mainly for
adminsitration/configuration and a number of public facing web applications
which can have a high load.
I have been experimenting with OSCache but the problem I se
