You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2015/03/17 18:30:39 UTC
[jira] [Updated] (QPID-6456) [AMQP 0-8] Java Broker sends wrong
connection close ok method identifier (51 rather than 61)
[ https://issues.apache.org/jira/browse/QPID-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall updated QPID-6456:
-----------------------------
Summary: [AMQP 0-8] Java Broker sends wrong connection close ok method identifier (51 rather than 61) (was: AMQP 0-8 Java Broker sends wrong connection close ok method identifier (51 rather than 61))
> [AMQP 0-8] Java Broker sends wrong connection close ok method identifier (51 rather than 61)
> --------------------------------------------------------------------------------------------
>
> Key: QPID-6456
> URL: https://issues.apache.org/jira/browse/QPID-6456
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.32
> Reporter: Keith Wall
> Fix For: 6.0 [Java]
>
>
> Owing to a defect in QPID-6125, the Java Broker current emits a connection.closeok with method id 51 rather than 61 when connected to a AMQP 0-8 peer. This causes interoperability problems with older clients that use the 0-8 protocol.
> For instance, the older Qpid 0-8 .NET client reports (seemingly harmlessly??):
> {noformat}
> 13 Mar 2015 07:01:03,299 WARN [Threadpool worker] Protocol.AMQProtocolListener: public void OnException(Exception cause = Apache.Qpid.Framing.AMQFrameDecodingException: Unable to find a suitable decoder for class 10 and method 51
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org