tendermint rpc with websocket client is not reconnecting

[KrishnaPG]

tendermint rpc with websocket client is not reconnecting

[KrishnaPG]

On the surface it seems to @willclarktech . Closing this for now.

[webmaster128]

Welcome @KrishnaPG and thanks for raising this issue. Which version of @iov/tendermint-rpc are you using? We are already working on reconnecting websocket connections automatically, which turns out to be quite hard.

In #1093 we added a reconnecting websocket that should in theory re-connect every time the connection drops. However, this does not re-subscribe to subscriptions.

If you could describe in more details what you try to do (preferribly with caller code) and what exactly does not work, we can try to understand the specific problem better.

[KrishnaPG]

Thank you @webmaster128

The version of @iov/tendermint-rpc used for this is: 1.2.0 (from npm)

I just put some debug breakpoints inside VS to step over the code and verify how to send the parameters correctly to the broadcastTxSync. The usage in this case was simple, something like below:

const { Client: TMintRPC } = require('@iov/tendermint-rpc');
this.tMintRPCClient = await TMintRPC.connect("ws://127.0.0.1:26657);

proposeBlock(data) {
    return this.tMintRPCClient.broadcastTxSync({ tx: data });
}

This works fine with http, but with ws even few seconds delay in stepping through the code just disconnects and does not reconnect afterwards for next call (even breakpoints are disabled for the next calls).

The culprit is in my opioin, the server side (tendermint node) is disconnecting the client and for some reason client is not able to detect it (which is evident by the fact that client is able to make the request, but server is unable to reply back). The server is what is throwing the error, not the RPCClient.

But if the RPC Client could detect the disconnection show how, (may be ping-pong?) and reestablish it, it may resolve it.

[willclarktech]

Thanks @KrishnaPG, would your issue be solved if #1200 was successfully closed?