[
https://issues.apache.org/jira/browse/DISPATCH-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16510026#comment-16510026
]
Gordon Sim commented on DISPATCH-1027:
--------------------------------------
I can't reproduce this. the cli-rhea-sender example in description seems to
work for me against router on master and 1.1.0. the client.html exaple from
rhea works as is (which include those protocols). I modified the client.js to
also include binary and amqp protocols and it also works.
> Cannot connect to router using WS when amqp protocol is specified
> -----------------------------------------------------------------
>
> Key: DISPATCH-1027
> URL: https://issues.apache.org/jira/browse/DISPATCH-1027
> Project: Qpid Dispatch
> Issue Type: Bug
> Affects Versions: 1.1.0
> Environment: client - rhea
> router - 1.1.0-RC3 (same issue is with previous versions)
> Reporter: David Kornel
> Priority: Major
>
> I cannot connect using websocket connection to router when http is enabled in
> listener when 'amqp' protocol is specified in websocket connection. I can
> only do that when only 'binary' is specified without 'amqp'. Otherwise I
> cannot connect to artemis using websocket when amqp is not specified.
> Router:
> {code:java}
> SERVER (info) Connection from 127.0.0.1 (to 0.0.0.0:5673) failed:
> amqp:connection:framing-error No valid protocol header found
> {code}
>
> Reproducer
>
> {code:java}
> npm install cli-rhea -g
> cli-rhea-sender --broker localhost:5673 --count 1 --conn-ws true
> --conn-ws-protocols binary amqp{code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
