Query/Question
We are using the SDK from an azure function on a service bus and notice the function sometimes suffers from socket exceptions / SNAT port exhaustion. It seems to be an issue using the SDK in the context of azure functions (our traffic isn't super high)
I've read that the SDK creates a new HTTP client for every request so (from searching online) pass the NotificationHubSettings a message handler created from a factory.
new NotificationHubSettings { MessageHandler = HttpMessageHandlerFactory.CreateHandler() });
I've noticed there is also a HttpClient I can set - should I create a static instance and pass that instead? I'm open to any suggestions!
Why is this not a Bug or a feature Request?
I'm looking for best practices to avoid port exhaustion from azure functions
Setup (please complete the following information if applicable):
Version of the Library used: 4.0.1
Azure functions v4 (Premium v3 P1V3)
Service bus
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report
Query/Question We are using the SDK from an azure function on a service bus and notice the function sometimes suffers from socket exceptions / SNAT port exhaustion. It seems to be an issue using the SDK in the context of azure functions (our traffic isn't super high)
I've read that the SDK creates a new HTTP client for every request so (from searching online) pass the NotificationHubSettings a message handler created from a factory.
new NotificationHubSettings { MessageHandler = HttpMessageHandlerFactory.CreateHandler() });I've noticed there is also a HttpClient I can set - should I create a static instance and pass that instead? I'm open to any suggestions!
Why is this not a Bug or a feature Request? I'm looking for best practices to avoid port exhaustion from azure functions
Setup (please complete the following information if applicable):
Service bus
Information Checklist Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report