use of closed network connection socket error read tcp XXXXXXX: use of closed network connection

[druphliu]

When subscribing to k-line data using the method futures.WsContinuousKlineServe, this error often occurs, causing the WebSocket (ws) connection to be interrupted. I have tried to ensure reconnection through the following methods,

for { doneC, _, err := futures.WsContinuousKlineServe(&futures.WsContinuousKlineSubscribeArgs{ Pair: symbol, ContractType: "PERPETUAL", Interval: interval, }, wsKlineHandler, errHandler) if err != nil { continue } <-doneC time.Sleep(time.Second * 10) }

but there is a problem. That is, the pushed data is lost during the reconnection process. How can this be solved?

[sc0Vu]

@druphliu Have you checked your network connection? The TCP error likely indicates a disconnection from the server.

[druphliu]

@druphliu Have you checked your network connection? The TCP error likely indicates a disconnection from the server.

yes,It is a server network and relatively stable

[minxtiny]

I also encountered this issue too, and switching to version 2.8.1 resolved it.

[batouy]

I also encountered this issue too, and switching to version 2.8.1 resolved it.

seems you are right

[sc0Vu]

What do you mean pushed data is lost during the reconnection? How can I reproduce this locally? The error means the software read from the closed TCP connection, it happened if the network is disconnected.

[druphliu]

The network has always been relatively stable, and this issue can steadily emerge. During the reconnection process, it is inevitable that the pushed data will not be received

[sc0Vu]

@druphliu Which environment did you use, testnet or mainnet? I wonder why change to 2.8.1 solved the issue? If the connection was unstable and reconnected, I think the data would be missed in that period and exchange api may push data later (because the writing on their side would be unstable).

[druphliu]

mainnet，I use the 2.8.2，this err always happen on the 2.8.1