Receiver node does not clear node_checkpoints upon double spend error

This was reported by client as a support ticket (SUP-719), and we were able to recreate the issue.

Detail:

In a transaction, in which initiator as well as receiver realises/fails the transaction with double spend, initiator clears the checkpoint table where as receiver does not.

• Faced this with corda enterprise 4.

• Log of recreation attached.

Initiator:
tx_id=C21AF7CB75A900FF8D8D6FF3DF21DD210295872893D8679FE8E063FAB4880ECC
flow-id=e66a11f5-bab9-4205-9996-08a70316ff8b
invocation_id=4e587ad2-6a06-4104-9229-a70fc35866ce
invocation_timestamp=2019-07-15T06:00:27.602Z
session_id=fd9cfe71-3e50-41e4-b5d3-b65f73d5baf4
actor_owning_identity=O=Bank Banana, L=New York, C=US

Receiver:
tx_id=C21AF7CB75A900FF8D8D6FF3DF21DD210295872893D8679FE8E063FAB4880ECC
flow-id=e8ab4c7a-793c-4779-91bf-e5e4dc5036fa
invocation_id=e5abbe5c-b0a1-4a46-97a7-f0e0f5fb841d
invocation_timestamp=2019-07-15T06:00:27.642Z
session_id=e5abbe5c-b0a1-4a46-97a7-f0e0f5fb841d
origin=O=Bank Banana, L=New York, C=US

Analysis

• db dump of initiator as well as receiver is attached

• db dump of initiator will not show flow-id=e66a11f5-bab9-4205-9996-08a70316ff8b in check point table

• db dump of receiver shows flow-id=e8ab4c7a-793c-4779-91bf-e5e4dc5036fa in its check point table.