Closed alrod closed 2 years ago
Based on the discussion on the issue, the goal here is to re-use connections to Service Bus across MessageReceivers and MessageSenders. We can start caching ServiceBusConnection objects keyed on the connection string and use this object when creating MessageReceiver and MessageSender objects instead of the connection string. @alrod do you feel we should continue caching the MessageReceiver and MessageSender as well in this case?
Any traction on this issue? We are starting to see issues as we add more ServiceBusTriggers to our Azure Function project.
is this can be refactored in track2?
https://github.com/Azure/azure-functions-servicebus-extension/issues/120#issuecomment-730653919