Re: proton 0.10 and swiftmq router
It looks like SwiftMQ is configured to require SASL authentication. If you supply authentication credentials (even "anonymous"), I believe this will work. -Ted On 10/02/2015 09:05 AM, Michael Ivanov wrote: Hallo, I am trying to run proton 0.10 client with SwiftMQ router and I'm getting the following errors: 3 2015-10-02 15:24:08.42/sys$amqp/ERROR/VersionedConnection, connection=127.0.0.1:55984/wrong header received: [ProtocolHeader, name=AMQP, id=0, major=1, minor=0, revision=0], required: [ProtocolHeader, name=AMQP, id=3, major=1, minor=0, revision=0], closing connection Swift MQ mailing list claims this is a proton issue :-\ Is there any hope to get a fix? Best regards,
proton 0.10 and swiftmq router
Hallo, I am trying to run proton 0.10 client with SwiftMQ router and I'm getting the following errors: 3 2015-10-02 15:24:08.42/sys$amqp/ERROR/VersionedConnection, connection=127.0.0.1:55984/wrong header received: [ProtocolHeader, name=AMQP, id=0, major=1, minor=0, revision=0], required: [ProtocolHeader, name=AMQP, id=3, major=1, minor=0, revision=0], closing connection Swift MQ mailing list claims this is a proton issue :-\ Is there any hope to get a fix? Best regards, -- \ / | | (OvO) | Mikhail Iwanow | (^^^) | Voice: +7 (911) 223-1300 | \^/ | E-mail: iv...@logit-ag.de | ^ ^ | |
[jira] [Closed] (PROTON-924) links are not uniquely named by messenger
[ https://issues.apache.org/jira/browse/PROTON-924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim closed PROTON-924. - Resolution: Duplicate > links are not uniquely named by messenger > - > > Key: PROTON-924 > URL: https://issues.apache.org/jira/browse/PROTON-924 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: 0.10 >Reporter: Gordon Sim > > If sending messages to different nodes in the same container, messenger will > establish multiple links but will use the same name - sender-xxx - for each > of them which violates the spec section 2.6.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PROTON-1008) Using a blank mech_list disables authentication
[ https://issues.apache.org/jira/browse/PROTON-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14941571#comment-14941571 ] ASF subversion and git services commented on PROTON-1008: - Commit baaf74ab7ab4ff699cbde374db1fdc2006eede0a in qpid-proton's branch refs/heads/master from [~gsim] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=baaf74a ] PROTON-1008: add toggle for sasl layer > Using a blank mech_list disables authentication > --- > > Key: PROTON-1008 > URL: https://issues.apache.org/jira/browse/PROTON-1008 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: 0.11 >Reporter: Ted Ross >Assignee: Gordon Sim > Fix For: 0.11 > > > This bug was introduced in commit > > https://github.com/apache/qpid-proton/commit/14956b07edc3de93f67179c753bbedcd9eba51a6 > If the client leaves allowed_mechs as None, the SASL protocol is not even > executed. I claim that allowed_mechs is used to restrict the set of > acceptable mechanisms. If it is None, then all available mechanisms may be > used. > This bug causes a failure in the Qpid Dispatch test suite > (system_tests_qdstat). The failure is when the server requires > authentication and will accept EXTERNAL and the client has a valid > client-certificate but doesn't use the sasl protocol because qdstat doesn't > (and can't) set the allowed_mechs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (PROTON-1008) Using a blank mech_list disables authentication
[ https://issues.apache.org/jira/browse/PROTON-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved PROTON-1008. Resolution: Fixed > Using a blank mech_list disables authentication > --- > > Key: PROTON-1008 > URL: https://issues.apache.org/jira/browse/PROTON-1008 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: 0.11 >Reporter: Ted Ross >Assignee: Gordon Sim > Fix For: 0.11 > > > This bug was introduced in commit > > https://github.com/apache/qpid-proton/commit/14956b07edc3de93f67179c753bbedcd9eba51a6 > If the client leaves allowed_mechs as None, the SASL protocol is not even > executed. I claim that allowed_mechs is used to restrict the set of > acceptable mechanisms. If it is None, then all available mechanisms may be > used. > This bug causes a failure in the Qpid Dispatch test suite > (system_tests_qdstat). The failure is when the server requires > authentication and will accept EXTERNAL and the client has a valid > client-certificate but doesn't use the sasl protocol because qdstat doesn't > (and can't) set the allowed_mechs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
