Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix consumer recovery with server-named queues #1325

Merged
merged 1 commit into from
Mar 23, 2023

Conversation

lukebakken
Copy link
Contributor

Port of #1324 to main

Fixes #1238

  • Add failing test
  • Fix RecordedConsumer to allow the empty string for a queue name
  • Add CurrentQueue to IChannel to keep track of the last declared queue name as defined in the AMQP 091 spec
  • Fix RecordedConsumer to use CurrentQueue when passed in name is string.Empty
  • Fixup API Approval

Port of #1324 to main

Fixes #1238

* Add failing test
* Fix `RecordedConsumer` to allow the empty string for a queue name
* Add `CurrentQueue` to `IChannel` to keep track of the last declared queue name as defined in the AMQP 091 spec
* Fix `RecordedConsumer` to use `CurrentQueue` when passed in name is `string.Empty`
* Fixup API Approval
@lukebakken lukebakken added this to the 7.0.0 milestone Mar 23, 2023
@lukebakken lukebakken self-assigned this Mar 23, 2023
@lukebakken lukebakken merged commit a9fe878 into main Mar 23, 2023
@lukebakken lukebakken deleted the rabbitmq-dotnet-client-1238-main branch March 23, 2023 22:15
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.

Autorecovery for server-named queues loops indefinitely when consumer listen this queue
1 participant