[API] When websockets server runs out of memory, it should exit so it can be restarted, instead of wedging.
Symptom: Pages not refreshing due to failure to connect to websockets
If I start a new instance, the page will not get refreshed that the job has started/running.
"Iceweasel can't establish a connection to the server at wss://ws.qr1hi.arvadosapi.com/websocket"
#10 Updated by Brett Smith almost 6 years ago
Peter Amstutz wrote:
Per Tom's comment in the description, let's try setting
Thread.abort_on_exception = trueand see if that breaks anything. The websockets server retains very little state so it is best to just kill it with extreme prejudice at the first sign of trouble.
Seems to be fine. Tested this locally with a hacked arv-ws that was rigged up to send a non-JSON string. That got back the "malformed request" response as expected. Then a normal arv-ws could connect without trouble. Now at 95d12ecb.