Hi Matthieu,
My answers are inlined.
On 20/04/2020 16:25, Matthieu Baechler wrote:
> Hi,
>
> [...]
>
> We studied a lot of solutions, ranging from having a standalone
ActiveMQ server to implementing the MailQueue using RabbitMQ or Kafka.
Why we chose RabbitMQ deserves an ADR don't you think?
>
Hi,
Sometime in the past, in the goal of having a fully-distributed James
implementation, we decided that the embedded ActiveMQ was something to
replace.
We studied a lot of solutions, ranging from having a standalone
ActiveMQ server to implementing the MailQueue using RabbitMQ or Kafka.
ActiveM
itmq-server/issues/959
> Introduce RabbitMQ as a MailQueue implementation
>
>
> Key: JAMES-2334
> URL: https://issues.apache.org/jira/browse/JAMES-2334
> Project: James Server
>
over topology when reconnecting. See
RabbitMQClusterTest.java .
James user will be subject to this limitation until bug is solved on RabbitMQ
level.
> Introduce RabbitMQ as a MailQueue implementation
>
>
>
[
https://issues.apache.org/jira/browse/JAMES-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tellier Benoit closed JAMES-2334.
-
> Introduce RabbitMQ as a MailQueue implementat
RabbitMQ
broker and its clustering mode
> Introduce RabbitMQ as a MailQueue implementation
>
>
> Key: JAMES-2334
> URL: https://issues.apache.org/jira/browse/JAMES-2334
> Project: James Serve
Antoine Duprat created JAMES-2334:
-
Summary: Introduce RabbitMQ as a MailQueue implementation
Key: JAMES-2334
URL: https://issues.apache.org/jira/browse/JAMES-2334
Project: James Server
