Skip to content

[azservicebus] Adding in the associated-link-name to all management link operations.#18291

Merged
richardpark-msft merged 3 commits intoAzure:mainfrom
richardpark-msft:sb-prepare-release
Jun 2, 2022
Merged

[azservicebus] Adding in the associated-link-name to all management link operations.#18291
richardpark-msft merged 3 commits intoAzure:mainfrom
richardpark-msft:sb-prepare-release

Conversation

@richardpark-msft
Copy link
Copy Markdown
Member

The associated-link-name property let's Service Bus know that a link is active, even if there is no direct activity on it.

For instance, when doing lock renewals you use the management link, but the associated receiver link is what you want to keep alive. We now pass this for all management related operations - scheduling messages, "backup" message settlement, lock renewal for messages and sessions, and session-state operations.

Fixes #16205

@richardpark-msft
Copy link
Copy Markdown
Member Author

/azp run go - azservicebus

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

Copy link
Copy Markdown
Member

@jhendrixMSFT jhendrixMSFT left a comment

Choose a reason for hiding this comment

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

One question but looks good.

@richardpark-msft richardpark-msft merged commit 6837144 into Azure:main Jun 2, 2022
@richardpark-msft richardpark-msft deleted the sb-prepare-release branch June 2, 2022 18:02
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.

[azservicebus] Ensure associated-link-name is properly set

3 participants