Hi Aleksey,
looking at the logs, it seems that the processor is actually doing a replay. I can see the statements:
15:41:03.778 INFO a.e.TrackingEventProcessor#ensureEventStreamOpened: Fetched token: null for segment: Segment[0/0]
15:41:03.841 WARN o.a.e.TrackingEventProcessor#processingLoop : Releasing claim on token and preparing for retry in 1s
15:41:04.853 INFO a.e.TrackingEventProcessor#ensureEventStreamOpened: Fetched token: null for segment: Segment[0/0]
…
15:41:04.866 WARN o.a.e.TrackingEventProcessor#processingLoop : Releasing claim on token and preparing for retry in 2s
15:41:06.876 INFO a.e.TrackingEventProcessor#ensureEventStreamOpened: Fetched token: null for segment: Segment[0/0]
The last log statement is the occurrence of a third failure, after which the test stops.
Another interesting aspect is that the test fails because it only found one invocation. In the logs above, you can see it was already invoked, twice at least.
What’s the behavior you observe in your real application that lead you to believe the processor stopped processing?
Cheers,
Allard