In some cases, org.eclipse.jetty.websocket.client.WebSocketClient.connect(listener, uri, request) call will return a future that never is completed. It is reasonable that our future.get() must have a timeout to avoid thread blocking.
I suggest something like:
		Callable<WebSocketSession> connectTask = () -> {
			Future<Session> future = this.client.connect(listener, uri, request);
                        try {
				// TODO Configurable timeout
				future.get(2000, TimeUnit.MILLISECONDS);
                        } catch (Exception ex){
                                 logger.error("Failed to connect to remote websocket endpoint", ex);
                                 future.cancel(true); // This method will stop the running underlying task
                        }
			return wsSession;
		};

Connection timeout is now associated to Jetty client timeout plus 50ms extra padding.

Timeout must consider also the idle timeout  of the Jetty client

Change idle Jetty max idle timeout for underlying HTTP Client