The AMQP output sends messages as transactions, which only guarantees delivery of a group of messages that have been sent as the transaction. Order of delivery is guaranteed, but order of consumption when there are multiple subscribers to a queue is arbitrary. In cases where there are multiple queue consumers, it may be difficult to know when all messages for a particular transaction have been handled.
Proposed solution
Add transaction marker messages containing headers to indicate:
Beginning of transaction
Transaction Id
The end of the transaction with the total number of messages to expect in the transaction
Add an additional headers to each message in the transaction that indicates:
Describe the problem
The AMQP output sends messages as transactions, which only guarantees delivery of a group of messages that have been sent as the transaction. Order of delivery is guaranteed, but order of consumption when there are multiple subscribers to a queue is arbitrary. In cases where there are multiple queue consumers, it may be difficult to know when all messages for a particular transaction have been handled.
Proposed solution
Add transaction marker messages containing headers to indicate:
Add an additional headers to each message in the transaction that indicates: