[FIXED] JWT max connections update closes internal clients #6785
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If the max connections on the JWT for an account is updated, connections over the limit will be closed. However, it would also close internal clients, like
SYSTEM
,JETSTREAM
, andACCOUNT
. This would result in publishing into the stream to fail (as well as any interactions with any other internal clients).Only close non-internal clients when the JWT's max connections is updated.
Resolves #6766
Signed-off-by: Maurice van Veen [email protected]