We have been getting reports of connectivity failures when sending new messages over our persistent websocket connection to our Blockbook instrastructure. The most used common case of failure is when adding new "watched addresses" (which is maintained on a per-connection basis). Aside from failure during new messages, there is not much other corelative behavior which is obviously triggering this disconnection.
We have been getting reports of connectivity failures when sending new messages over our persistent websocket connection to our Blockbook instrastructure. The most used common case of failure is when adding new "watched addresses" (which is maintained on a per-connection basis). Aside from failure during new messages, there is not much other corelative behavior which is obviously triggering this disconnection.
This issue manifests as an error in the logs from the multiwallet indicating that the websocket has died and is reconnecting via https://github.com/OpenBazaar/openbazaar-go/blob/f3499105bfdb834cddf365e140f391ffac0033f8/vendor/github.com/OpenBazaar/multiwallet/client/blockbook/client.go#L48.