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 2022/08/16 02:52:00 UTC
[jira] [Closed] (JAMES-3801) RabbitMQ should NACK mail items it did fail to load
[ https://issues.apache.org/jira/browse/JAMES-3801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benoit Tellier closed JAMES-3801.
---------------------------------
Resolution: Fixed
> RabbitMQ should NACK mail items it did fail to load
> ---------------------------------------------------
>
> Key: JAMES-3801
> URL: https://issues.apache.org/jira/browse/JAMES-3801
> Project: James Server
> Issue Type: Bug
> Components: rabbitmq
> Affects Versions: 3.7.0
> Reporter: Benoit Tellier
> Priority: Major
> Fix For: 3.8.0
>
> Attachments: Screenshot from 2022-08-10 10-49-47.png
>
>
> See JAMES-3800
> We do encounter a timeout on top of OVH S3 blob store when reading emails.
> RabbitMQMailQueue, upon loading exception, does not really handle those exception and let them propagate to the subscriber, here JamesMailSpooler, which handles the exception by just logging it.
> THis means the RabbitMQ messages of such emails are never acked nor nacked, stays unacknowledged forever. Unacknowledged messages keeps pile up until there is no space left for legitimate traffic.
> At this point the mailQueue consumption halts, James needs to be rebooted which effectively nack those messages.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org