Uploaded image for project: 'Qpid JMS'
  1. Qpid JMS
  2. QPIDJMS-480

Connection creation hangs if WS transport drops before handshake completes

    XMLWordPrintableJSON

    Details

    • 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
    • Labels:
      None

      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).

        Attachments

          Activity

            People

            • Assignee:
              robbie Robbie Gemmell
              Reporter:
              siano Stephan Siano
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: