Reconnect Strategy #2117
Replies: 3 comments 6 replies
-
@sachin-kiwi Can you attach an error listener to the client and then see what error it's returning? For example: client.on('error', (error) => { /* code here to detect what type of disconnect error */ } Also adding a listener for |
Beta Was this translation helpful? Give feedback.
5 replies
-
How to control num of attempts for reconnect manually. |
Beta Was this translation helpful? Give feedback.
1 reply
-
@sachin-kiwi If you would like to still receive additional help, please reopen the discussion. Closing due to inactivity. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
While working with the library I faced the issue
NotConnectedError: connect ECONNREFUSED 35.85.20.122:51233 at Connection.onConnectionFailed
I found that there can be a few reasons.
Then I look into handling the such a situation and found this by xrpl
#1101
Now, I am trying to implement a connection strategy to handle this scenario in production.
Can you give me some insight on reconnect method in xrpl.Client?
Beta Was this translation helpful? Give feedback.
All reactions