I have a self-hosted NSB process that may start publishing events as soon as it is started. In my observation, when the internal NSB runtime starts up, it will start processing subscription requests on a separate thread (not the one where a publish request is received) with a delay of a couple of seconds. Then in this scenario, the new subscribers, although having their subscription request submitted before the "opening of the store", will still miss the first few publishes after "the store is opened".
How can I force NSB to do the first publish only after having completed all subscription requests already submitted in queue at the start of the process?