-
Notifications
You must be signed in to change notification settings - Fork 25
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
Unhandled i/o timeout error leads to infinite busy loop in startResponseRouter() function #61
Comments
As you can see, recovering doesn't help, management link won't recover. |
I think there are two issues here.
Does that sound right? |
Indeed, the RPC client lives on the Queue itself, not the Receiver, so recovering it would have no effect. |
There is third problem here - RPC link doesn't refresh auth token, but that's another story. |
Please, consider my changes not as a final solution, but as a code, illustrating problems found. |
Hi,
Is this related to this i/o issue? |
@sruthiramani without more details it's hard to say. Can you please open a new issue and provide relevant info like version and which API call(s) you see returning this error? |
I've opened a new issue with the details |
Expected Behavior
No busy loop, properly handling of network errors.
Actual Behavior
When i/o timeout error occurs, startResponseRouter() function enters busy loop here:
Environment
The text was updated successfully, but these errors were encountered: