[
https://issues.apache.org/jira/browse/JAMES-4033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-4033.
---------------------------------
Resolution: Fixed
> Option for EventBus to not propagate error when already store failed event in
> Dead Letter
> -----------------------------------------------------------------------------------------
>
> Key: JAMES-4033
> URL: https://issues.apache.org/jira/browse/JAMES-4033
> Project: James Server
> Issue Type: Improvement
> Components: eventbus, rabbitmq
> Reporter: Tran Hong Quan
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> ## Why
> Today given e.g. RabbitMQ is down, EventBus can not dispatch the event to
> RabbitMQ, and it would persist the event into the dead letter (in the
> database).
> Today even when the event is stored in the dead letter, EventBus still
> propagates the error back and fails the original caller IMAP APPEND or IMAP
> STORE for example (while the mail is stored and just Added event has not been
> processed yet while being in dead letters).
> Given today we are more or less robust on auto reprocessing the failed event
> (from event dead letters), we could consider not propagating the error back
> and failing the original call.
> ## How
> Add a boolean configuration entry in `rabbitmq.properties` to enable/disable
> EventBus error propagation upon storing failed events in dead letters.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
