[rabbitmq-discuss] question, Shovel : different queue name between source and destination

bino oetomo bino at indoakses-online.com
Sat May 19 02:50:23 BST 2012

Dear Brendan and All
I really appreciate your enlightment
On 05/18/2012 07:00 PM, Brendan Hay wrote:
> In fairness, I probably over complicated things by trying to be as explicit
> as possible with the config.
> But here is my updated gist containing a 'publish_fields' addition to
> ensure the messages go to the destination exchange:
> https://gist.github.com/2723964
It works !
blasting fast
> With that adjustment, you should be able to publish a message to
> 'source_exchange' without a routing key, and have it turn up in
> 'destination_queue'.
for those who just first-day-er (or in my case : Old crack brainer) with 
rabbitMQ, just adopt 
just be carefull about all 'name'
> Here are also a couple of things you can do to assist in debugging shovel
> problems:
> Firstly tailing the logs under /var/log/rabbitmq will show any specific
> authentication/vhost errors the shovel has while starting up.
Yup .. I did
> The shovel management plugin can be enabled via: rabbitmq-plugins enable
> rabbitmq_shovel_management
> This will let you see the status of the shovel via a tab in the management
> ui.
I did
> PS. If you are running the shovel plugin as either the source or
> destination for the configuration then you can specify the amqp uri as just
> "amqp://".
> The shovel plugin will then use guest on vhost '/' via the amqp direct
> connection - this is a good. You can read more about the direct connection
> here: http://www.rabbitmq.com/erlang-client-user-guide.html#model

Again, I really appreciate your enlightment


More information about the rabbitmq-discuss mailing list