[rabbitmq-discuss] Shovel with exchange-exchange bindings

Mon Jul 25 12:06:50 BST 2011

Thank you very much Matthew. Now, isn't there a chance that you have some spare time to add the max-hops option to the shovel addin as well? ;)
Because all I'm trying to do with these tricks is what I would accomplish with that.. I am already working on it, I've been able to build the addin and its dependencies on Ubuntu - which is unfamiliar environment for me - but my erlang-fu is still not very good.

As a side note,  as mentioned in another thread, shovel has a dependency on erlando, which is not documented in the readme.

-----Original Message-----
From: rabbitmq-discuss-bounces at lists.rabbitmq.com [mailto:rabbitmq-discuss-bounces at lists.rabbitmq.com] On Behalf Of Matthew Sackman
Sent: Monday, July 25, 2011 12:57 PM
To: rabbitmq-discuss at lists.rabbitmq.com
Subject: Re: [rabbitmq-discuss] Shovel with exchange-exchange bindings

Hi Simone,

On Mon, Jul 25, 2011 at 09:45:09AM +0000, Busoli, Simone wrote:
> I'm trying to set up a shovel with exchange-exchange bindings to 
> workaround the issue with infinite loops when configuring a symmetric 
> shovel between two brokers (to achieve transparent bidirectional 
> communication), but I get an error on broker startup as if the shovel 
> didn't support exchange-exchange bindings.
> 
> As suggested by Matthew some time ago on the list this is what I'm 
> trying to accomplish:
> 
>               /---------------------[ Shovel 2 ]---------------------\
>               |                                                      |
>               V                                                      |
> --->[X1]--->[X2]---->[[my queues]]        [[my queues]]<---[X2]<---[X1]<---
>      |                                                       ^
>      |                                                       |
>      \------------------[ Shovel 1 ]-------------------------/

That's a very pretty picture ;)

> But on broker startup I get  this:
> 
> {"Kernel pid 
> terminated",application_controller,"{application_start_failure,rabbitm
> q_shovel,{{invalid_shovel_configuration,test1,{invalid_parameter_value
> ,sources,{unknown_method_name,'exchange.bind'}}},{rabbit_shovel,start,
> [normal,[]]}}}"}
> 

Yup. I've just fixed this on default - if you pull from our hg repos, update, and compile again, then you'll get it working though check the README because a few other things have changed in the mean time (like support for confirms has been added, and support for transactions has been removed).

In short, the problem was that the shovel predated Rabbit's support of AMQP 0-9-1. When 0-9-1 was added, the shovel seems to have been forced to check only 0-8 methods. As such, it didn't have support for our extensions to 0-9-1 (at least from configuration - the actual erlang client being used does connect using 0-9-1 and uses those features that we've added, such as confirms). Anyway, fixed now.

Many thanks for the bug reports - the shovel will clearly benefit!

Matthew
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss at lists.rabbitmq.com
https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

_________________________________________________________________________________________________________________
Questo messaggio e da intendersi esclusivamente ad uso del destinatario e puo contenere informazioni che sono di natura privilegiata, confidenziale
o non divulgabile secondo le leggi vigenti. Se il lettore del presente messaggio non e il destinatario designato, o il dipendente/agente responsabile
per la consegna del messaggio al destinatario designato, si informa che ogni disseminazione, distribuzione o copiatura di questa comunicazione e 
strettamente proibita anche ai sensi del decreto legislativo 196/03 . Se avete ricevuto questo messaggio per errore, vi preghiamo di notificarcelo
immediatamente a mezzo e-mail di risposta e successivamente di procedere alla cancellazione di questa e-mail e relativi allegati dal vostro sistema.
_________________________________________________________________________________________________________________
This message is intended only for the use of the addressee and may contain information that is privileged, confidential and exempt from 
disclosure under applicable law. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the 
message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly 
prohibited. If you have received this e-mail in error, please notify us immediately by return e-mail and delete this e-mail and all attachments from 
your system.
_________________________________________________________________________________________________________________