-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Transient error occurred: The link '...' is force detached #34588
Comments
We restarted our pods, and they started getting the error after about 26 minutes. In the mean time no messages were received. It's not immediately obvious from the logs why no messages were received during those 26 minutes:
|
Update on the issue. We have two different services. One receiving messages, one sending messages. When then service that stopped receiving messages, as per the error described in this issue, we had made a change to the sending service, where we started sending batch messages. However, we had made an error where we sent a list of messages as a single message, instead of a batch message. For some unknown reason, the receiving service stopped receiving messages at the same time in our production environment. In our testing environment, the receiving service continued to receive messages, but they would just fail at being mapped, due to the wrong data type, but that's just our fault. We have tried restarting both the sending and receiving service many times, without any change to the situation. We then tried deleting the queue and creating a new one. Both the sending and receiving service threw errors during the downtime that they could not find the queue, as would be expected. When the queue was recreated, the sending service automatically reconnected and resumed sending messages to the queue. The receiving service stopped throwing the error described in this issue, but did not receive messages. After restarting the receiving service, it now receives messages as normal again. We have no idea why the change in sending messages would result in messages not being received in one environment (production), but not another (test). Likewise, we have no idea why it started working again. |
Update on the issue. We discovered a bug in our usage of the Regardless, we solved the above bug, and have since gotten a much more stable usage. However, we still experience the error about 1 time per week. The error does not resolve itself, unless we restart the service. Coupled with the fact that there is no health indicator on the client (#21976), we have to manually start the service, which is pretty bad. Since the initial bug report, we have also updated our Azure dependencies, and are currently using the following versions:
|
Hi @AndreasPetersen, thank you for the detailed write up. @anuchandy will follow up here. Please note that if this is an urgent issue that we recommend creating an Azure Support ticket rather than a GitHub issue: https://github.com/Azure/azure-sdk-for-java/blob/main/SUPPORT.md#azure-support-tickets |
Hi @joshfree , thanks for the reply. In fact we just created a support ticket a few days ago. I have already referred to this issue. |
Hello @AndreasPetersen, I'm closing this given that there is no more down time since you switched to the beta library and iiuc the application is receiving without interruption for ~1.5 months at this point. |
Describe the bug
After running our service since 2023-04-19 around 15:00, on 2023-04-20 at around 12:40 our services stops receiving messages. There are no warning or error messages saying why. At 16:57 the services starts receiving the errors below. This continues until at least 2023-04-21 10:00 where I'm writing this bug report. Meanwhile no new messages are received.
We are running two pods on a Kubernetes cluster, and the error occurred on both pods at the same time.
I can see that there are related issues reported, but these are closed and locked: #18890, #32919
Exception or Stack Trace
Specifically the warning/error logs. The rest are included for context.
The errors occurs every 10 minutes.
To Reproduce
Steps to reproduce the behavior:
Unknown
Code Snippet
Expected behavior
Being able to re-establish connection and continue receiving messages.
Setup (please complete the following information):
com.azure:azure-messaging-servicebus:7.13.0
andcom.azure:azure-identity:1.5.4
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
The text was updated successfully, but these errors were encountered: