EHC ❯ failure to replicate to one peer shouldn't prevent others

• Type: Bug
• Status: Closed
• Priority:
• Resolution: Fixed
• Component/s:
• Labels:

• Assignee: drb
• Reporter: sourceforgetracker
• Created: September 21, 2009
• Votes: 0
• Watchers: 0
• Updated:

  September 22, 2009
• Resolved:

  September 22, 2009

Description

In RMISynchronousCacheReplicator.java, line 129, replicatePutNotification method:

There is a for loop that iterates through all the peers, trying to “put” against each one. When the first “put” fails, the exception will bubble up. Thus, the “put” is never attempted to peers after the first one that fails. I think you should try against all peers - it doesn’t make sense (to me, at least) that if one peer fails, that all peers that happen to be in the list after that one should never receive the replication messages. Sourceforge Ticket ID: 2018964 - Opened By: craigandrews - 15 Jul 2008 21:24 UTC

Comments

Fiona OShea 2009-09-22

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