[
https://issues.apache.org/jira/browse/QPID-5224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13793786#comment-13793786
]
Robbie Gemmell commented on QPID-5224:
--------------------------------------
I had a look at this, and unfortunately it turned out to be the result of the
JMS client making use of a Qpid extension to AMQP which RabbitMQ doesn't
support, leading it to close the connection when it was encountered. The
particular usage of this extension causing the problem was added to the client
in the 0.24 release, so using an older client release should remove that issue
with the consumer. Unfortunately older clients have an issue with producers
against RabbitMQ 3.x (as per QPID-5184).
In order to resolve the issue, the particular use of the extension that was
added in 0.24 will be escaped with a check that it is Qpid on the other end so
that it isnt used when connecting to RabbitMQ, thus stopping it killing the
connection and allowing the consumer creation to proceed.
> [Java 0-x Client] connection is abruptly closed when creating consumers
> against RabbitMQ
> ----------------------------------------------------------------------------------------
>
> Key: QPID-5224
> URL: https://issues.apache.org/jira/browse/QPID-5224
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.24
> Environment: Qpid 0.24 AMQP 0-x client, RabbitMQ 2.x / 3.x
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Fix For: 0.25
>
>
> When using the Qpid 0.24 AMQP 0-x JMS client, attempting to create consumers
> against a RabbitMQ broker results in the connection being abruptly closed.
> Reported by a user in this thread:
> http://mail-archives.apache.org/mod_mbox/qpid-dev/201310.mbox/%3C1381164667512-7599126.post%40n2.nabble.com%3E
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
