[
https://issues.apache.org/jira/browse/JAMES-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17048759#comment-17048759
]
Benoit Tellier commented on JAMES-3080:
---------------------------------------
https://github.com/linagora/james-project/pull/3159 solved this for the
distributed task manager.
I wonder to what extent these findings can apply to the mailqueue and the
eventBus.
> Make messages persistent in rabbitmq task manager workqueue
> -----------------------------------------------------------
>
> Key: JAMES-3080
> URL: https://issues.apache.org/jira/browse/JAMES-3080
> Project: James Server
> Issue Type: Improvement
> Reporter: Rémi Kowalski
> Priority: Major
>
> 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 workqueue 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: [email protected]
For additional commands, e-mail: [email protected]
