It’s me again with again EventHandlers
We discovered that using a defaultSequencingPolicy = SequentialPolicy in combination with segmentation does not properly work. In our test application it does not work in 9 of 10 cases.
It can happen that when you start the application some events are processed fine and then all of a sudden the event handling stops working. It can also happen that you start the application and the event handlers are not triggered at all.
When you start launching 2 applications (2 threads each, 4 segements) one of the apps stops handling events and the other continues for a while. We though see in the logs messages like “Notifying handlers for phase XXXX”
We didn’t test the behaviour during a replay yet. What of course works totally fine is single threaded processing.
This whole thing seems pretty random. We do not see any exceptions and it’s a bit frustrating at this point. There are cases where we need to insure a sequential handling of events. At this point we do not have a lot of information we just observed this behaviour now for a while and cannot figure out exactly what is going on.
We even deleted tracking tokens and tried to “replay” everthing from scratch and the problems reoccurred.
Are there any known limitations (or issues) regarding SequentialPolicy and segmentation/multi-threaded event-handling? At least on github I couldn’t find anything nor in the documentation.