We sometimes have events which’s handling ends up with an exception during commit of the respective transaction.
We would like to put those events to some kind of DLQ, in order to let the user decide what to do with them.
I know that you can use an ErrorHandler to handle the error and to let the (in our case TrackingEventProcessor) EventProcessor continue (no retry then).
That works fine so far, but: when I restart the microservice, event handling restarts at the event where the error occurred. I would expect this not to happen, but the event handler to start off with the next new event.
What am I doing wrong?