[
https://issues.apache.org/jira/browse/JAMES-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3082.
---------------------------------
Resolution: Fixed
https://github.com/linagora/james-project/pull/3166 contribute this along with
tests
> Make messages persistent in rabbitmq eventbus
> ---------------------------------------------
>
> Key: JAMES-3082
> URL: https://issues.apache.org/jira/browse/JAMES-3082
> Project: James Server
> Issue Type: Improvement
> Reporter: Rémi Kowalski
> Priority: Major
> Fix For: 3.5.0
>
>
> Regarding the persistence of messages in rabbitmq : To achieve this there are
> two steps :
> the queue must be declared as durable (the declaration of the queue is
> persisted rabbitmq is restarted)
> when sending a message, it must have a property setting its delivery_mode to
> persistent. (the messages with this property are persisted in case of a
> restart of rabbitmq)
> At the time being the rabbitmq eventbus in james :
> the queue is declared durable => Good
> the delivery_mode property is not set => Not good
> the exchange is not declared durable => Seems not good, but need testing
> What should be done is :
> set the `delivery_mode` property to '2' ( see
> https://www.rabbitmq.com/releases/rabbitmq-java-client/v2.4.1/rabbitmq-java-client-javadoc-2.4.1/index.html?com/rabbitmq/client/MessageProperties.html
> )
> verify if the exchange need to be declared 'durable' too. if so it will need
> an entry in the migration guide. As it will need to be deleted an created
> back with the new properties.
--
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
