Hi,
Thank you for the response.. how can re-establish the connection after LB is up again ? Can we configure it in the RabbitMQ WEb UI ?
we have not written any client code to recover consumers... we have prebuild Collector, Executor and Delivery queue libraby which is using rabbitmq engine in config and Nginx LB IP in rabbitmq.config fila,
we can't modify the queue in the WEB UI, so we have setup a policy to mirror the rabbitMq node and tried to set up the Dead letter Exchange and Routing Key in the same policy to reroute the Unack messages again to the queue, but it seems to be not working.''
Testing : we are putting the files in the folder so that Collector is collectting the files and processing through (using RabbitMq message queue ) the Executor and Delivery and showing the processed files in EDI.
We have set the policy like this whereas collectorQueue is showing in the web from our application :-
Pattern \w*
Apply to queues
Definition
dead-letter-exchange: collectorQueue
dead-letter-routing-key: collectorQueue
ha-mode: exactly
ha-params: 2
ha-sync-mode: automatic
queue-mode: lazy
Is it correct set up for DLX and routing key ? we have not set up any Exchanges, do we need to create an exchange for the DLX to show up or we can directly set it to Collector queue
Thanks in advance.
Regards,
Sunita