When a topic subscription is fulfilled within the subscriber's process, the subscription request is not sent to the master. This is because there is nothing in place yet to stop a double subscription (one local, and one via TCP due to the master's notification of a publisher).
The fix is simple: register the subscription with the master, but ensure that local subscriptions preclude subsequent remote subscriptions.
When a topic subscription is fulfilled within the subscriber's process, the subscription request is not sent to the master. This is because there is nothing in place yet to stop a double subscription (one local, and one via TCP due to the master's notification of a publisher).
The fix is simple: register the subscription with the master, but ensure that local subscriptions preclude subsequent remote subscriptions.