I am running with JBoss 3.2.3 with both clustering and cache-invalidation enabled. When I was looking at the performance I noticed that the cache-invalidation service appears to not only invalidate the remote caches but also the local cache as well.
I can see that this might be useful if I have an ejb deployed as readonly as well as read-write but in my case I just have one deployed ejb.
This means that every time I update the ejb, the cache is invalidated and a load is forced the nexst time I access the ejb! I might as well use commit option B...
What am I missing? Is this a configuration issue or what?