I'm using the WebSocket API's to connect to EDP data for Futures FX and Equities. Over the last 3 days at random intervals I stop receiving data over the WebSocket and on the next re-auth attempt I get an exception back from the WebSocket client with the "returned an error (400) bad request" message.
The request I'm making is no different than the hundreds before it that succeeded.
There are 2 major problems - 1) we stop getting data and 2) there is no good way to know in the code until the next returh attempt where I receive the bad request message. Please note that I am still pinging back and forth on the open connection.
I don't know what other information I can provide - this is not the first time we've seen thsi but it is now happening every day. We are still having entitlments added/changed so I also want to make sure it's not just a function of that causing this problem.
I believe if I completely shutdown everything internally, reconnect with a clean connection and resub I will continue to get data, but there will be a gap in the data at this point.