[
https://issues.apache.org/jira/browse/QPIDJMS-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated QPIDJMS-480:
-----------------------------------
Fix Version/s: 0.48.0
> Connection creation hangs if WS transport drops before handshake completes
> --------------------------------------------------------------------------
>
> Key: QPIDJMS-480
> URL: https://issues.apache.org/jira/browse/QPIDJMS-480
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
> Affects Versions: 0.46.0, 0.47.0
> Reporter: Stephan Siano
> Priority: Minor
> Fix For: 0.48.0
>
>
> 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).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
