There are 2 problems:

• None of A, B, C or D are coordinators, so while everybody sends merge information, nobody actually runs the view consistency checker, so nobody would inject a MERGE event into the system. I don't want to change this (I only want coordinators to run the view consistency check), to avoid unneeded processing
• If we revert to the old behavior when determineActualMergeCoords() returns an empty list, we'd run into the old problem, where B is supposed to trigger the merge but doesn't as it is not in the coordinator role.

This could be fixed by having everyone (coordinator and participant roles) handle merge notifications (and this was actually my first fix for JGRP-1451), but this creates unnecessary processing, e.g. I don't want everyone to handle merge notifications in a large cluster.