cancel
Showing results for 
Search instead for 
Did you mean: 

Event Mesh - Messages disappear in Dead Message Queue of a Dead Message Queue concept

MarkvanDooren
Explorer
0 Kudos

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.

100985314489
Explorer
0 Kudos

Hello,

Were you able to achieve this scenario? Is there any workaround in getting this done?

Thanks!

MarkvanDooren
Explorer
0 Kudos

Hi Sai,

Unfortunately we were not able to achieve the scenario.

We have build a workaround: When errors occur CPI will send the events to the DeadMessageQueue via the AMQP Adapter. The DeadMessageQueue itself is still using the TimeToLive expiry DeadMessageQueue functionality and processes the Events back to the Processing Queue.

Regards,

Mark

mk_eventmesh
Explorer
0 Kudos

Hi,

Could you please share the screenshot? how you achieved the scenario ?
It would be very helpful if you could share the screenshot of SAP CPI.
Do we need to use AMQP receiver adapter at the end of the iflow and need to give the queue name ?

Kavita_Achari
Newcomer
0 Kudos

Hello @MarkvanDooren ,

Could you please tell us if this issue was solved? What was the workaround you implemented to solve this issue?

Thanks

Accepted Solutions (0)

Answers (0)