Steven van Beelen

Adjusted priority to a "should" and removed milestone. This issue requires changes in Axon Server which are less pressing on the list. Furthermore, it is not feasible that this will...

Thanks for sharing your input here @jnfeinstein. As it stands we are actively pursuing a likely new type of Event Processor which will allow for parallelization, without the hard requirement...

The described issue is mitigated perfectly by using the `PooledStreamingEventProcessor` instead of the `TrackingEventProcessor`. So for those who are hitting this predicament, please try out the Pooled Streaming Processor instead...

Closing this issue as we feel the `PooledStreamingEventProcessor` sufficiently covers for the scenario.

Thanks for filing this issue with us, @vab2048. I'd wager there's merit in aligning the `JdbcSagaStore` with the `TokenStore` and `EventStorageEngine`. As stated, it's not overly complex to work around...

This would firstly require a change in how we return the query handler type throughout the system, as it currently doesn't not deal with `ParameterizedTypeImpl` I think. Secondly, I think...

The only scenario that introduces this possibility for a test fixture in action, is the `FixtureConfiguration#getRepository`. The remaining occasions that initialize the `Repository` are forms of `given`, which change the...

A work around would be to ensure you have as little gaps as possible. Typically, you should not have to many gaps, ever, but sometimes a misconfiguration in the sequence...

A note stating that a dedicated sequence generator should be used for the `globalIndex` field of the `domain_event_entry` would indeed not hurt anybody. As far as strategies go, the framework...

@mbreevoort both the `JpaEventStorageEngine` and `JdbcEventStorageEngine` allow for configuring the "gap timeout" and "gap cleaning threshold". The former marks a gap "old" and removable, whilst the second marks the max...