glime-ai[bot]
commented
1 week ago To address the issue of subscriptions not being deleted from Azure Service Bus namespaces, you should ensure that your implementation includes a mechanism to clean up these subscriptions once they are no longer needed. This can be done programmatically by using the Azure Service Bus SDK to delete subscriptions when they are no longer in use.
Here are some steps you can take to resolve the issue:
-
Review your code to ensure that you have logic in place to delete subscriptions after they are no longer needed. Subscriptions should be deleted programmatically using the Azure Service Bus SDK.
-
Check for any exceptions or errors in your application logs that might indicate why subscriptions are not being deleted as expected.
-
If you are using the MassTransit library with Azure Service Bus, ensure that you are correctly configuring the bus to manage subscriptions. MassTransit provides features to automatically remove subscriptions when they are no longer in use.
-
If you are using the Elsa Workflow library with Azure Service Bus, review the Elsa documentation and ensure that you are following best practices for managing resources with the service bus.
-
If the issue persists, consider reaching out to the Azure Service Bus or the respective library's support channels for further assistance.
Please note that without specific code examples or error messages, it's challenging to provide a more detailed solution. If you can provide additional information about how you are managing Azure Service Bus subscriptions in your application, I can offer more targeted advice.
This comment was generated by Glime.
Description
Subscriptions for deleting temporary subscriptions which are no longer used are no longer being deleted from Azure Service Bus namespaces. This causes the number of subscriptions and therefor the storage per topic to increase since the message can no longer be picked up from these subscriptions. This in turns leads to exceptions.