[jira] [Closed] (JAMES-3871) No eventBus associated to EventDispatcher$DispatchingFailureGroup

["Benoit Tellier (Jira)" <se...@james.apache.org>]

     [ https://issues.apache.org/jira/browse/JAMES-3871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benoit Tellier closed JAMES-3871.
---------------------------------
    Resolution: Fixed

> No eventBus associated to EventDispatcher$DispatchingFailureGroup
> -----------------------------------------------------------------
>
>                 Key: JAMES-3871
>                 URL: https://issues.apache.org/jira/browse/JAMES-3871
>             Project: James Server
>          Issue Type: Bug
>            Reporter: Tung TRAN
>            Priority: Trivial
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> *Error:*
> {code:java}
> logger org.apache.james.webadmin.service.EventDeadLettersRedeliverService
> message No eventBus associated. event: EventId
> {id=db0dcdc2-0f2d-4736-8da6-1057e3d9179e}
> for group: org.apache.james.events.EventDispatcher$DispatchingFailureGroup
> {code}
>  
> *Reason:*
> The `EventDispatcher$DispatchingFailureGroup` has not been registered for event bus correspondence.
> *How to fix:*
>  - Create a EventBusName POJO into event-bus-api
>  - Create a custom Group for DispatchingFailureGroup in event-bus-api, with the EventBusName in it. (With serialization, deserialization)
>  - Use EventBusName into existing naming strategy (replaces String prefix)
>  - In EventDeadLettersRedeliverService handle DispatchingFailureGroup differently: use the EventBusName to find the right event bus.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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