[JAMES-4033] Option for EventBus to not propagate error when already store failed event in Dead Letter

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Component/s: eventbus, rabbitmq
• Assignee: Unassigned
• Reporter: Tran Hong Quan
• Created: 14/May/24 05:44
• Updated: 03/Jun/24 13:26
• Resolved: 03/Jun/24 13:26

Description

1. 1. 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.

1. 1. How

Add a boolean configuration entry in `rabbitmq.properties` to enable/disable EventBus error propagation upon storing failed events in dead letters.

 

Issue Links

• links to: GitHub Pull Request #2245