[QPIDJMS-480] Connection creation hangs if WS transport drops before handshake completes

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 0.46.0, 0.47.0
• Fix Version/s: 0.48.0
• Component/s: qpid-jms-client
• Assignee: Robbie Gemmell
• Reporter: Stephan Siano
• Created: 13/Nov/19 09:42
• Updated: 29/Jan/20 13:45
• Resolved: 14/Nov/19 17:46

Description

If you try to connect to a qpid-jms client with the amqpws (without TLS) transport to an SSL enabled server supporting the websocket protocol, the connection will hang (instead of failing with an error).

You can reproduce the issue if you change line 60 of NettyWsTransportTest to 

return new NettyEchoServer(options, true, needClientAuth, true);

and execute testConnectToServerUsingCorrectPath().

The test is expected to fail, but it fails only because the test times out after 60 seconds, not because the connection fails. Without that test timeout, the connection will hang indefinitely.

 

If I try something similar with a TCP transport (connecting with amqp to an amqps) server, this fails after 10 seconds, which looks like a timeout to me (and is something I would consider ok).