Details
-
Bug
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
-
0.8.3-beta1
-
None
Description
Closing connection must be handle "synchronously", meaning that previous call results must be handled before closing the connection.
Current implementation doesn't do that resulting in different error like "Connection is closing" or "unexpected message received when no command was send"