I believe it fixes #282 #202

Why not just change the interval here:

How did you come up with 3 minutes?

@mkurz The 3 minutes is from the Binance documentation.

The reason I am not changing it in the ServiceGenerator, is because the same client is used for the http connections, and they probably don't have the same pingInterval.

The 3 minutes is from the Binance documentation.

The ping/pong from the documentation has nothing to do with the pingInterval you are changing here. The ping/pong documented (where the server is sending the ping and the client is answering with pong) is handled already by underlying okhttp, there is not even a setting to change any interval for that.

The pingInterval of the line I referred to or that you want to change now, is not even necessary (that's a ping the client will send and the server will answer with a pong). We could completely remove it and the client will still work (and the server ping/client pong will still be working and handled by underlying okhttp).
The pingInterval was just added so the client will faster recognice if the connection got aborted.

The reason I am not changing it in the ServiceGenerator, is because the same client is used for the http connections, and they probably don't have the same pingInterval.

I highly doubt that pingInterval is used by a http connection at all. You send a request, you get an answer, connection closed, AFAIK.

It says in the documentation that it's used for both HTTP/2 and websocket connections. It probably does not affect the http calls made from this Binance client, so I would just remove it from the shared http client, and set it only for the websockets client with an appropriate value.

You are right, pingInterval does not affect the server initiated ping-pongs, to which the documentation is referring. But setting it to 20 secs, just makes the client too eager to drop perfectly good connections (I was still receiving messages, when getting the exception). So setting it to 3 mins, to mirror what the server is doing seems reasonable.

I totally agree. 20 seconds seems far to less.
BTW: You are referring to okhttp docs 4.x, however binance-java-api is using 3.x.

It says the same for okhttp 3.X

It seems to me that this is still an issue and @eugenpodaru isn't active anymore. Any plans to fix this?