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

2024-05-13 Thread Tran Hong Quan (Jira)
Tran Hong Quan created JAMES-4033:
-

 Summary: 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


## 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: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org



[BUILD-FAILURE]: Job 'james/ApacheJames/master [master] [1363]'

2024-05-13 Thread Apache Jenkins Server
BUILD-FAILURE: Job 'james/ApacheJames/master [master] [1363]':
Check console output at "https://ci-builds.apache.org/job/james/job/ApacheJames/job/master/1363/";>james/ApacheJames/master
 [master] [1363]"

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org