Skip to content

[FIXED] Only forward shadow subs if we are not a leafnode or a hub leafnode client#5519

Merged
derekcollison merged 1 commit intomainfrom
issue-5473-2
Jun 11, 2024
Merged

[FIXED] Only forward shadow subs if we are not a leafnode or a hub leafnode client#5519
derekcollison merged 1 commit intomainfrom
issue-5473-2

Conversation

@derekcollison
Copy link
Copy Markdown
Member

Resolves: #5473

Signed-off-by: Derek Collison derek@nats.io

…lient.

Signed-off-by: Derek Collison <derek@nats.io>
@derekcollison derekcollison requested a review from a team as a code owner June 11, 2024 15:14
Copy link
Copy Markdown
Member

@neilalexander neilalexander left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@derekcollison derekcollison changed the title [FIXED} Only forward shadow subs if we are not a leafnode or a hub leafnode client [FIXED] Only forward shadow subs if we are not a leafnode or a hub leafnode client Jun 11, 2024
@derekcollison derekcollison merged commit e173373 into main Jun 11, 2024
@derekcollison derekcollison deleted the issue-5473-2 branch June 11, 2024 15:43
wallyqs added a commit that referenced this pull request Jun 11, 2024
Includes the following:

* #5515
* #5516 
* #5517
* #5519
* #5514 
* #5521 
* #5522 

Signed-off-by: Neil Twigg <neil@nats.io>
kozlovic added a commit that referenced this pull request Sep 4, 2025
This is related to PR #5519 where the propagation of a shadow subscription
was suppressed for a subscription coming from a spoke leafnode connection,
but the handling of the unsubscribe of such shadow subscription was not
fixed, which could result in removing a legitimate interest.

The test `TestLeafNodeDupeDeliveryQueueSubAndPlainSub` that was added
in PR #5519 was modified to demonstrate what would have been the issue
without the fix in this PR.

Signed-off-by: Ivan Kozlovic <ivan@synadia.com>
derekcollison added a commit that referenced this pull request Sep 5, 2025
…ode (#7259)

This is related to PR #5519 where the propagation of a shadow
subscription was suppressed for a subscription coming from a spoke
leafnode connection, but the handling of the unsubscribe of such shadow
subscription was not fixed, which could result in removing a legitimate
interest.

The test `TestLeafNodeDupeDeliveryQueueSubAndPlainSub` that was added in
PR #5519 was modified to demonstrate what would have been the issue
without the fix in this PR.

Signed-off-by: Ivan Kozlovic <ivan@synadia.com>
MauriceVanVeen pushed a commit that referenced this pull request Sep 5, 2025
This is related to PR #5519 where the propagation of a shadow subscription
was suppressed for a subscription coming from a spoke leafnode connection,
but the handling of the unsubscribe of such shadow subscription was not
fixed, which could result in removing a legitimate interest.

The test `TestLeafNodeDupeDeliveryQueueSubAndPlainSub` that was added
in PR #5519 was modified to demonstrate what would have been the issue
without the fix in this PR.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Message duplication with leafnode connection

2 participants