On our dev setup we have the SubscriptionRebuildAfterFileChangeListener enabled. Now we sometimes run into issue when subscriptions need to be rebuilt: the data of some of these projectors is needed on kernel request listeners that run relatively early with high priority (e.g. tenant configuration).
What happens is:
- at priority 200: AutoSetup
- at priority 128: our logic throws as an exception because data from the subscription is missing
- at priority 100:
SubscriptionRebuildAfterFileChangeListener runs
For comparison, the SessionListener runs at 128. I would suggest to bring the priorities closer together, as there is somewhat a functional dependency between these.
For now I re-arranged priorities of our listeners, so we won't run into this for a while. but others might as well..
On our dev setup we have the
SubscriptionRebuildAfterFileChangeListenerenabled. Now we sometimes run into issue when subscriptions need to be rebuilt: the data of some of these projectors is needed on kernel request listeners that run relatively early with high priority (e.g. tenant configuration).What happens is:
SubscriptionRebuildAfterFileChangeListenerrunsFor comparison, the
SessionListenerruns at 128. I would suggest to bring the priorities closer together, as there is somewhat a functional dependency between these.For now I re-arranged priorities of our listeners, so we won't run into this for a while. but others might as well..