Replica Deadlock

Description

Note:
This article pertains to ArcGIS versions 9.x only. Later versions of ArcGIS may contain different functionality, as well as different names and locations for menus, commands and geoprocessing tools.

When using disconnected replication a deadlock situation occurs where both replicas are data receivers with the same generation numbers (in their replica properties).

Cause

This is caused by the following workflow:

1. A two-way replica is created.
2. A data change message is exported from the secondary (DC1) with a switch message. This changes the secondary replica to a data receiver.
3. DC1 is imported into the primary replica.
4. A data change message is exported (DC2) from the primary with a switch message. This changes the primary to a receiver.
5. DC2 is imported into the secondary replica.
6. DC2 is then imported into the primary with a switch message.

Note:
This should be blocked, now both replicas are senders with the same generation numbers.

7. Data changes (DC3) are then exported from the primary with a switch message.
8. Data changes (DC4) are then exported from the secondary with a switch message.

Solution or Workaround

Note:
This issue occurs in ArcGIS versions 9.2, 9.3, and 9.3.1 only. This problem does not occur in later versions.