We’re facing a weird issue that kept us busy for days now, currently on Axon FW/Server 4.4 (we tried the same on 4.5 though).
We’ve implemented 3 tracking event processors (which update the same MongoDB projections) and due to concurrency it sometimes comes to exceptions due to optimistic locking.
In order to catch those exceptions and retry, we’ve configured the ListenerInvocationErrorHandler to be a PropagatingErrorHandler.
Upon such an exception, retry is said to be starting (which is okay), but now comes the weird part.
Instead of repeating to process the events that caused the exception in the event handler/processor, Axon processes the next events. It looks like the “pointer” to the token store is not reset.
Any help would be very much appreciated.