• Bug
  • Status: Closed
  • Resolution: Fixed
  • drb
  • Reporter: sourceforgetracker
  • September 21, 2009
  • 0
  • Watchers: 0
  • September 22, 2009
  • September 22, 2009


Hi *,

I want to invalidate the elements in my peer caches everytime an element is updated. As far as I understood the documentation setting replicateUpdatesViaCopy to false should result in a removal of the updated element in all peers.

Unfortunately the setting below (using replicateUpdatesViaCopy=false) does not work.

I have a little sample application. Two peers, both of them contain elements with the same keys (key0 to key9). If I remove an element in one cache the removal is replicated, puts are replicated, updates are replicated as updates not as invalidations.

My cache configuration:

I used ehcache-1.4.0-beta as well as ehcache-1.3.0.

Best regards

Martin Sourceforge Ticket ID: 1794695 - Opened By: martinkirchner - 14 Sep 2007 12:44 UTC


Sourceforge Tracker 2009-09-21

Logged In: YES user_id=693320 Originator: NO


RMICacheReplicatorTest#testUpdateViaInvalidate proves that replicateUpdatesViaCopy.

In short I cannot reproduce the problem. Please show how this fails by modifying that test or with something similar.

Thanks Greg Comment by: gregluck - 23 Dec 2007 05:13 UTC

Fiona OShea 2009-09-22

Re-opening so that I can properly close out these issues and have correct Resolution status in Jira