Better handling for database issues in Websockets

The Websocket connections should be able to handle database disconnects and pick up connections again after the database reconnected. This currently works if the Websocket was established when the database was still connected, but Websocket connections are simply denied when the database is not connected.

I guess this is an edge case and not a very high priority though.