Project

General

Profile

Actions

Bug #4591

closed

[API] When websockets server runs out of memory, it should exit so it can be restarted, instead of wedging.

Added by Bryan Cosca over 10 years ago. Updated over 10 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
API
Target version:
Story points:
0.5

Description

Symptom: Pages not refreshing due to failure to connect to websockets

bcosc:
If I start a new instance, the page will not get refreshed that the job has started/running.

Peter:
"Iceweasel can't establish a connection to the server at wss://ws.qr1hi.arvadosapi.com/websocket"

Tom:
http://ruby-doc.org/core-2.1.4/Thread.html#method-c-abort_on_exception-3D ?


Subtasks 1 (0 open1 closed)

Task #4701: Review 4591-websockets-raise-oom-wipResolvedBrett Smith12/02/2014Actions

Related issues 1 (0 open1 closed)

Has duplicate Arvados - Bug #4623: No auto-update of pipeline times in browserClosed11/20/2014Actions
Actions

Also available in: Atom PDF