Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
0.20.0
-
None
Description
The client (and underlying it, proton-j) doesnt currently handle this scenario well, say for example attempting to connect to a server not using a SASL layer when it expects SASL be used, or not using AMQP at all. It should notice the issue and fail-fast, but can await the connection process to timeout instead.
Depends on PROTON-1426 + PROTON-1427, and in turn QPIDJMS-270 to get them.