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


There might be a small problem in the MulticastReceiverThread class (MulticastKeepaliveHeartbeatReceiver.java, Rev. 52, line 132). The self(String rmiUrl) method checks whether the incoming URL is matching the first entry in the list of cache peers (which is - I guess - it’s own address). This works if two Java processes run on different machines (with different IP addresses).

When using two Java processes that want to share the cache on the same machine, this check does not work, because both VMs have the same IP address and multicast-port. In my scenario, both processes use the same configuration file, but as far as I understand the configuration settings, I think this is not a problem.

To solve this issue (if it is one ;), I would propose to use a (semu-)unique ID that every cache manager creates at startup and uses it until it is terminated. This ID could be added to the payload that is sent to the other peers. (e.g., the URL could instead of // look like //;id= or //

Hope that helps, Roman Sourceforge Ticket ID: 1483735 - Opened By: roman_k - 8 May 2006 10:56 UTC


Fiona OShea 2009-09-22

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