WSO2 Micro Integrator message processor issue with RabbitMQ 3.10.0

[Shanmukh Shankar]

Hello Team,

Background:

We have a WSO2 Micro Integrator 4.1.0 ESB application which stores messages into RabbitMQ 3.10.0 (Erlang 23.3.4.11).  The message processor on wso2 has an indefinite retry mechanism.

Issue:

when a consumer is not responding, message processor keeps on retrying. I see the message remains in Unack status in the rabbitmq queue. After 30 min, message moves into Ready status (i suspect because of dead letter??). Now the wso2 message processor is not able to process this message. 

Tested the same issue with Rabbitmq 3.8.0 (erlang 22), and even after 30 min of retry the wso2 message processor was still able to process message which is in Ready status.

It would be great help if anyone can provide some insight into this issue from rabbitmq perspective if this is expected behavior.

Thanks in advance.

Shanmukh

[Luke Bakken]

Hi  Shanmukh,

Without knowing how this application is written all we can do is make guesses. Do you have logs from the application and RabbitMQ?

If a message is in Un-acked status and then moves to Ready in the same queue, it may be because the consumer has closed its channel and/or connection, in which case RabbitMQ will re-enqueue the message.