azure-sdk-for-go: [azservicebus] Timeout in ReceiveMessages
Bug Report
-
pkg:
github.com/Azure/azure-sdk-for-go/sdk/messaging/azservicebus -
SDK version:
v0.3.2 -
go version:
go 1.16.2 -
What happened? We recently moved from
azure-service-bus-goand implemented an asb client usingazure-sdk-for-go. This implementation was working fine for few days and then started to give below timeout error frequently. A manual service restart seem to fix the issue temporarily, but after some time error appears again in the logs. Our implementation is supposed to retry retrieving messages indefinitely but it doesn’t seem to recover from the error and getting the messages from the topic. Pls note we are subscribing to multiple topics using multiple clients here. You can find our client implementation here. Error:Failed to receive messages from ASB. read tcp 1*.*.*.113:xxxxxx->**.*.*.88:xxxx: i/o timeout -
What did you expect or want to happen? If something unexpected causes this timeout error we expect it to recover when retrying.
-
Anything we should know about your environment. Our service is running on AKS
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 1
- Comments: 22 (8 by maintainers)
Commits related to this issue
- [azservicebus] reset connection on network failures (#17048) There are some errors coming from go-amqp that indicate internal or fatal errors with the connection. At the moment go-amqp does not recov... — committed to Azure/azure-sdk-for-go by richardpark-msft 2 years ago
- [azservicebus] Handle 410 properly for session and non-session based links. (#17382) 410 (lock lost) handling needed to be separated for sessions and non-session links. For non-session links losin... — committed to Azure/azure-sdk-for-go by richardpark-msft 2 years ago
(sorry for the late response, was on vacation)
For this fix you can do a
go geton the commit hash.