You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The log is flooded with errors like the following once the queue is removed
2022-07-04 10:12:10.4912|124|Warn|NServiceBus.Transport.AzureServiceBus.MessagePump|Failed to receive a message. Exception: Put token failed. status-code: 404, status-description: The messaging entity 'sb://test20200605.servicebus.windows.net/Particular.Servicecontrol' could not be found. To know more visit https://aka.ms/sbResourceMgrExceptions. TrackingId:30d5270c-ecae-4ed9-9b3c-c4981b5c2623_G0, SystemTracker:test20200605.servicebus.windows.net:Particular.Servicecontrol, Timestamp:2022-07-04T08:12:10. (MessagingEntityNotFound)
Azure.Messaging.ServiceBus.ServiceBusException: Put token failed. status-code: 404, status-description: The messaging entity 'sb://test20200605.servicebus.windows.net/Particular.Servicecontrol' could not be found. To know more visit https://aka.ms/sbResourceMgrExceptions. TrackingId:30d5270c-ecae-4ed9-9b3c-c4981b5c2623_G0, SystemTracker:test20200605.servicebus.windows.net:Particular.Servicecontrol, Timestamp:2022-07-04T08:12:10. (MessagingEntityNotFound)
If the queue does not exist either the service should quit and not start or wait until it exists and have a backoff strategy.
The text was updated successfully, but these errors were encountered:
The log is flooded with errors like the following once the queue is removed
If the queue does not exist either the service should quit and not start or wait until it exists and have a backoff strategy.
The text was updated successfully, but these errors were encountered: