When the participants are primed, the participants reports back acknowledgment message with the status "PRIMED" immediately, but in the runtime db the status was not updated to PRIMING yet. Because of the conflict, the runtime mishandles the acknowledgement message and fails to update the participant status as PRIMED.

 

Log:

*[2023-04-03T09:22:08.680+00:00|INFO|network|DMAAP-source-POLICY-ACRUNTIME-PARTICIPANT] [IN|DMAAP|POLICY-ACRUNTIME-PARTICIPANT]

{"responseTo":"9a2bd6af-75ad-4ec5-b0e1-63576baa64ff","result":true,"message":"Participant Prime Ack message","messageType":"PARTICIPANT_PRIME_ACK","compositionId":"689cead0-aeea-40ef-b25c-b15b7ef2740c","participantId":"101c62b3-8918-41b9-a747-d21eb79c6c01","state":"ON_LINE"}

[2023-04-03T09:22:08.732+00:00|WARN|SupervisionHandler|DMAAP-source-POLICY-ACRUNTIME-PARTICIPANT] AC Definition 689cead0-aeea-40ef-b25c-b15b7ef2740c already primed/deprimed with participant 101c62b3-8918-41b9-a747-d21eb79c6c01*