Eugene Schava
Eugene Schava
If reconnection is handled by the client code every call of disconnect() and connecting again creates a new thread while the old one still lives
Kraken: optionally limit the rate of WebSocket messages sent to the server to avoid "Exceeded msg rate" error message
Otherwise, checksum calculation fails too often (if the server book doesn't match local one)
I use "changed nodes only" mode for deploy but state machine sends current state even if it isn't changed I think it could be related to "nodes-started" event processing when...
Memory is leaking if that method is called many times
Otherwise, messages might be reordered if min interval is 0
The error happens when instructing class like ``` public class Main { public synchronized static boolean h() { return true; } } ```