The documentation mentions that the SimpleEventBus will stop event processing if an exception is encountered in any of the event listeners and rightly so, as the publish logic is simply for a for loop that pushes subscribed events to event listeners…To avoid termination of event listener, the use of the ClusteringEventBus was recommended…
But the ClusteringEventBus appears to be a little too much for my current use case…clustering event listeners, working with task executers, introducing concurrency etc
Is there a way to easily assemble a middle ground? Where the setup is as simple as what the SimpleEventBus provides but tolerant to exceptions in event listeners? Without having to go the Clustering event bus route?