Messages for durables possibly sent before Subscription response #930
Assignees
Labels
Comments
kozlovic
added a commit
that referenced
this issue
Sep 3, 2019
Original issue was addressed in PR #247, but unfortunately the fix did not take into account durable subscriptions. If a durable subscription is restarted, the subscription object is in memory and would have the flag "initialized" already set to true, which would not prevent published messages at the time of the subscription request processing to allow messages to be sent prior to the subscription response. Resolves #930 Signed-off-by: Ivan Kozlovic <ivan@synadia.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If a durable subscription is closed (not unsubscribed) and later restarted while new messages are being published, it is possible that messages are sent prior to the subscription response protocol.
This is not visible in most of the client libraries since the subscription create usually holds a lock that is required during processing of the incoming messages.
However, this is not the case in Node.js.
The text was updated successfully, but these errors were encountered: