You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This client currently does not handle disconnects, be it just a network error or the complete node fails.
Expectation
Either throw on connection failure or reconnect.
Current behaviour
it breaks completely, every subsequent request just throws errors that it can't connect to the server even though it is running again. Only restarting the application helps.
so once i make a call and no server is available it first throws errors and after that it wont stop throwing on subsequent request. If I however do not make a request while the server is down and it is back available again before the next, for some strange reasons everything works.
We talk by the way about spawning, the handler just silently dies and does nothing anymore forever.
The text was updated successfully, but these errors were encountered:
Moving from wrong repo burstable/node-beanstalkd-client#6
Description
This client currently does not handle disconnects, be it just a network error or the complete node fails.
Expectation
Either throw on connection failure or reconnect.
Current behaviour
it breaks completely, every subsequent request just throws errors that it can't connect to the server even though it is running again. Only restarting the application helps.
so once i make a call and no server is available it first throws errors and after that it wont stop throwing on subsequent request. If I however do not make a request while the server is down and it is back available again before the next, for some strange reasons everything works.
We talk by the way about spawning, the handler just silently dies and does nothing anymore forever.
The text was updated successfully, but these errors were encountered: