Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
0.23.0
-
None
Description
During the SASL authentication process there's a change that an error thrown from the handler code in the exchange phases can result the wrong exception being thrown from the connection create methods in the ConnectionFactory due to a race between asynchronous notifications and the exception thrown from the connect call.