You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Benoit Tellier (Jira)" <se...@james.apache.org> on 2019/11/04 11:26:00 UTC
[jira] [Closed] (JAMES-2937) RabbitMQMailQueue does not recover
from network outage
[ https://issues.apache.org/jira/browse/JAMES-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benoit Tellier closed JAMES-2937.
---------------------------------
Resolution: Fixed
https://github.com/linagora/james-project/pull/2741 enforced reactor primitive usage when working with RabbitMQ, addressing some stability and performance issues.
https://github.com/linagora/james-project/pull/2807 contributed a test for this.
> RabbitMQMailQueue does not recover from network outage
> ------------------------------------------------------
>
> Key: JAMES-2937
> URL: https://issues.apache.org/jira/browse/JAMES-2937
> Project: James Server
> Issue Type: Bug
> Components: rabbitmq
> Reporter: René Cordier
> Priority: Major
> Fix For: 3.5.0
>
>
> When there is a network outage issue, the dequeue on RabbitMQ seems to fail. RabbitMQMailQueue is the only part of the code not using reactor-rabbitMQ for publishing messages.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org