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 2014/07/19 14:58:38 UTC
[jira] [Commented] (QPID-4693) Make Qpid client communicating with
RabbitMQ broker
[ https://issues.apache.org/jira/browse/QPID-4693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14067513#comment-14067513 ]
Keith Wall commented on QPID-4693:
----------------------------------
I am not able to reproduce this exception with Qpid Client 0.29 and Rabbit 3.3.4, so given the age/inactivity of this Jira, I mark as Cannot Reproduce.
2014-07-19 13:35:18,228 DEBUG [main] [protocol] SEND: [org.apache.qpid.client.protocol.AMQProtocolHandler@2e3fe12e] Frame channelId: 1, bodyFrame: [ExchangeDeclareBodyImpl: ticket=0, exchange=amq.direct, type=direct, passive=true, durable=false, autoDelete=false, internal=false, nowait=false, arguments=null]
The rabbit server is processing this command without error. I wonder if there has been a change on the Rabbit side (since 3.0.4) it no longer validates for matching arguments when passive=true.
There are system properties that can be used to turn off exchange/queue declare behaviour on the Qpid Client:
http://qpid.apache.org/releases/qpid-0.28/jms-client-0-8/book/JMS-Client-0-8-System-Properties.html#idm223934163888
> Make Qpid client communicating with RabbitMQ broker
> ---------------------------------------------------
>
> Key: QPID-4693
> URL: https://issues.apache.org/jira/browse/QPID-4693
> Project: Qpid
> Issue Type: Wish
> Components: Java Client
> Affects Versions: 0.20
> Reporter: Kyle
> Priority: Trivial
> Labels: newbie
>
> Hi all,
> I have a question about interoperability between Qpid client and RabbitMQ broker.
> Currently, I use Qpid-client-0.20 connecting to RabbitMQ-3.0.4 broker(Erlang R16B).
> I have met a problem is that my consumer could not receive the message from a queue. Obviously my producer sent a message to this queue already.
> When I dug in the code, I saw that:
> - Each peer transferred messages with different format and order. It makes protocol header and protocol version failed, therefore precondition of broker is failed.
> - By default design, RabbitMQ broker defines exachanges as durable while Qpid clients does different way as non-durable. It makes precondition failed too.
> connection <0.491.0>, channel 1 - soft error:
> {amqp_error,precondition_failed,
> "cannot redeclare exchange 'amq.direct' in vhost '/test' with different type, durable, internal or autodelete value",
> 'exchange.declare'}
> - Framing errors were occurred between communication of both peers
> Did someone try with the latest qpid client and rabbitmq broker and make them communicated?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org