Older concurrent changes are never replicated

When a (non-conflicting) change is made in two replica peer servers (A and B) at once, A's changes are replicated to B, but B's changes are never replicated to A. This leads to inconsistent trees. The two changes made can be totally unrelated (e.g. setting an attribute in two separate objects).

This is easy to reproduce by having two replica servers set up, disabling the network link, making a separate change on each server,then re-enabling the network link. Only one server will have both changes, the other will only have its own change.