-
Notifications
You must be signed in to change notification settings - Fork 586
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
Cannot receive messages for the client scope subscription #726
Comments
Could you share Azure CLI or Bicep scripts to provision this as on my end I can't reproduce the issue. |
I still have the same issue with 5.0.15/ I am using Terraform to spin up the subscription. The service bus namespace has geo disaster recovery enabled and the connection string is using an alias connection string instead of a plain connection string. For geo-disaster recover please check https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-geo-dr
|
We try to use the client-scoped subscription in our product and when we use the Azure service bus explorer to receive messages, it throws an exception. As you see here if the subscription is client scoped subscription as
test_article$ClientId$D
, it will not allow processing due to sub-queue name being invalid.<16:10:08> The subscription test_article$ClientId$D for the article topic has been successfully retrieved. <16:10:08> The rule $Default for the test_article$ClientId$D subscription of the host2wms_article topic has been successfully retrieved. <16:29:11> Exception: Provide a valid sub-queue name. The allowed values are: '$DeadLetterQueue'. Parameter name: name
For more details on client-scoped subscriptions, please check this link:
https://learn.microsoft.com/en-us/azure/service-bus-messaging/java-message-service-20-entities#representation-of-client-scoped-subscriptions
Tool version :
The text was updated successfully, but these errors were encountered: