SendAsync InvalidOperationException

[AceHack]

Actual Behavior

1. When calling SendAsync I sometimes get InvalidOperationException System.InvalidOperationException: Can't create session when the connection is closing. at Microsoft.Azure.ServiceBus.Core.MessageSender.OnSendAsync(IList1 messageList) at Microsoft.Azure.ServiceBus.RetryPolicy.RunOperation(Func1 operation, TimeSpan operationTimeout) at Microsoft.Azure.ServiceBus.RetryPolicy.RunOperation(Func1 operation, TimeSpan operationTimeout) at Microsoft.Azure.ServiceBus.Core.MessageSender.SendAsync(IList1 messageList) at Arch.TestService.ServiceBusTest.RunAsync() in /build/src/Arch.TestService/ServiceBusTest.cs:line 131

Expected Behavior

1. To always work when calling SendAsync

Versions

• OS platform and version: docker container microsoft/dotnet:2.1.5-aspnetcore-runtime-stretch-slim
• .NET Version: core 2.1.5
• NuGet package version or commit ID: 3.2.0

[axisc]

@AceHack - do you see this issue when sending messages after a long while. Inactive connections may be closed depending on how you set up the connection.

could you share a repro?

[AceHack]

It’s random, I’m just sending a 20 byte message in a loop every one second. Also there is a message lock exception that happens sometimes too.

[AceHack]

Also, the abstraction for TopicClient is an always working connection. I should not see any errors unless there are actual network errors, it uses fault tolerant amqp connection underneath. I'm using the default retry strategy as well so it should have handled this.

[SeanFeldman]

Also there is a message lock exception that happens sometimes too.

Lock exception on a message sent out?

[axisc]

if you still see this issue, please open a support ticket. closing this issue for now.