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 "Matthieu Baechler (Jira)" <se...@james.apache.org> on 2020/06/18 19:51:00 UTC
[jira] [Closed] (JAMES-3070) RabbitMQ MailQueue should not share
Receiver for several purpose
[ https://issues.apache.org/jira/browse/JAMES-3070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthieu Baechler closed JAMES-3070.
------------------------------------
Resolution: Fixed
Merged
> RabbitMQ MailQueue should not share Receiver for several purpose
> ----------------------------------------------------------------
>
> Key: JAMES-3070
> URL: https://issues.apache.org/jira/browse/JAMES-3070
> Project: James Server
> Issue Type: Improvement
> Components: Queue
> Reporter: Matthieu Baechler
> Priority: Major
>
> "spool" MailQueue is used in several places in James code.
> The usage pattern is quite different in those different places.
> While trying to control accurately the rate of James dequeue, we found that sharing a single RabbitMQ Receiver can prevent from passing it specific parameters at construction.
> We should try make James work without the MailQueue sharing for RabbitMQ.
--
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