Benoit Tellier created JAMES-3605:
-------------------------------------
Summary: RabbitMQ reconnection handlers should restart consummers
Key: JAMES-3605
URL: https://issues.apache.org/jira/browse/JAMES-3605
Project: James Server
Issue Type: Bug
Components: rabbitmq
Affects Versions: master
Reporter: Benoit Tellier
Fix For: 3.7.0
## Why?
After upgrading RabbitMQ to 3.8.17 we noticed that, once in a while, messages
were not consumed anymore. The consumers alocated to it died and were not
replaced.
This results in emails / updates being delayed.
## Possible explanation
For any reason (GC, network failure) some timeout was exceeded and the
connection deemed unusable.
Upon connection replacement, no attempt is made to resume the consumer.
## Current fix
Restart James.
## Expected behaviour
We expect James, upon connection replacement, to happily restart its consumers.
## How?
Reconnection handler should also resume consummers.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
