azure service bussss session processor

[lifejoyforpy]

trafficstars

Library name and version

Azure.Messaging.ServiceBus 7.5.1

Describe the bug

i use c# 7.5.1 Azure.Messaging.ServiceBus sdk , use session queue consumer message . language is c# .aspnetcore web . cause Azure.Messaging.ServiceBus.ServiceBusException: The session lock has expired on the MessageSession. Accept a new MessageSession. this exception cause my new message cannot consumer( some new message cannot execute by MessageHandler ) . how to consumer this message .

Expected behavior

1

Actual behavior

Azure.Messaging.ServiceBus.ServiceBusException: The session lock has expired on the MessageSession. Accept a new MessageSession.

Reproduction Steps

1

Environment

aspnet core web 3.1

[jsquire]

Thank you for your feedback. Tagging and routing to the team member best able to assist.

[lifejoyforpy]

[JoshLove-msft]

This means that the session lock has expired. The session processor will eventually attempt to receive from the same session again. The reason for this happening could be that processing took longer than the configured MaxAutoLockRenewalDuration, or there may have just been a transient network outage that caused the link to be lost. You can find more info about possible exceptions here - https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/servicebus/Azure.Messaging.ServiceBus/TROUBLESHOOTING.md#find-information-about-a-servicebusexception.

[ghost]

Hi @lifejoyforpy. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text “/unresolve” to remove the “issue-addressed” label and continue the conversation.

[ghost]

Hi @lifejoyforpy, since you haven’t asked that we “/unresolve” the issue, we’ll close this out. If you believe further discussion is needed, please add a comment “/unresolve” to reopen the issue.