Skip to content

GH-5202: keep the ASB response queue identity stable during startup - #5203

Merged
jeremydmiller merged 1 commit into
JasperFx:mainfrom
DeandreT:fix/asb-response-queue-5202
Oct 24, 2026
Merged

jeremydmiller merged 1 commit into
JasperFx:mainfrom
DeandreT:fix/asb-response-queue-5202

Conversation

@DeandreT

Copy link
Copy Markdown
Contributor

Fixes #5202.

Keep the Azure Service Bus response queue's first node identifier when database registration changes AssignedNodeNumber. Resource setup and runtime initialization then use the same queue, without changing AutoProvision or control-queue behavior.

Add regression coverage for resource setup, repeated discovery, prefixes, Solo mode, and PostgreSQL-backed startup with the Service Bus emulator.

@DeandreT
DeandreT marked this pull request as ready for review October 24, 2026 03:52
@jeremydmiller
jeremydmiller merged commit 5c048ca into JasperFx:main Oct 24, 2026
47 checks passed
This was referenced Oct 25, 2026
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.

Azure Service Bus response queue is not created after the node number changes during startup

2 participants