on 02-09-2022 9:03 AM
Hi All,
We are trying to build the following EventMesh concept solution:
Event Mesh receives messages in the Processing Queue via the AMPQ protocol. SAP Cloud Integration will process messages from the Processing Queue via the AMQP protocol. When message processing raises an error in SAP Cloud Integration and MaxRetries is reached, AMQP status REJECTED will be reported by SCI to EventMesh and the message will be moved to the Dead Message Queue. This is working.
The Dead Message Queue has option Respect Time to Live Enabled. When the Time to Live expires Event Mesh should move the message from the Dead Message Queue to the Dead Message Queue of the Dead Message Queue (which is the original Processing Queue). This is not working. When the Time to Live expires, the message is removed from the Dead Message Queue, but is not moved to the Processing Queue. The message is gone.
Is this concept of using two queues which are Dead Message Queues of each other, supported?
We have tested the Respect Time to Live mechanism for a regular message in a regular Processing Queue and then it is working fine. So it looks like it is only not working in the concept of using a Dead Message Queue of the Dead Message Queue.
The reason could be that the Dead Message Queue needs to exist when the Processing Queue is created. In a circular reference this is of course not possible because both Queues are using the other queue as Dead Message Queue.
For now it looks like we cannot use the concept because the messages disappear.
User | Count |
---|---|
83 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.