I confirm that the web client library makes no assumption about the unavailability of the Server and just keeps retrying to connect.
At application level, you can leverage onStatusChange or getStatus and check how long the Engine remains in "CONNECTING" state with your own timer;
if needed, you can switch to "DISCONNECTED" state, then issue an alert.