Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
3.4.7
-
None
-
None
Description
There are several issues related to websocket connection opening that are surfaced when the there isn't a server listening in the provided address.
To list the issues:
- Open is made in the background, that could cause unhandledRejection.
- Race condition between error handling and opening, causing the promise to resolve and/or the process to exit (depending on the case).
We should refactor how Connection#open() is invoked by the Client to always check that open was previously called and fix the race condition.
Attachments
Issue Links
- causes
-
TINKERPOP-2708 unhandledRejection upon connection failure
- Closed