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
I'm using the management SDK to call my hub from a functions project. The code effectively looks like this with the appropriate connection string and hub name.
public static class MyFunction
{
[FunctionName("MyFunction")]
public static async Task Run([TimerTrigger("0 */10 * * * *")]TimerInfo myTimer, ILogger log, ExecutionContext executionContext)
{
var connectionString = "";
var serviceManager = new ServiceManagerBuilder()
.WithOptions(option =>
{
option.ServiceTransportType = ServiceTransportType.Persistent;
option.ConnectionString = connectionString;
})
.Build();
var hub = await serviceManager.CreateHubContextAsync("myhub");
await hub.DisposeAsync();
}
}
When I use the persistent transport type, I can see server connections leaking on Azure. When I drill into an individual transaction I see that immediately after the dispose is called and the transport stopped, it opens again,
I also see this behaviour locally with the above code.
The text was updated successfully, but these errors were encountered:
I'm using the management SDK to call my hub from a functions project. The code effectively looks like this with the appropriate connection string and hub name.
When I use the persistent transport type, I can see server connections leaking on Azure. When I drill into an individual transaction I see that immediately after the dispose is called and the transport stopped, it opens again,
I also see this behaviour locally with the above code.
The text was updated successfully, but these errors were encountered: