[rabbitmq-discuss] Shunting messages from one queue to another

Tom Anderson tom.anderson at timgroup.com
Wed Jul 3 16:13:05 BST 2013

On 03/07/13 13:03, Simon MacMullen wrote:
> On 03/07/13 12:43, Michael Klishin wrote:
>> 2013/7/3 Tom Anderson <tom.anderson at timgroup.com
>> <mailto:tom.anderson at timgroup.com>>
>>     I don't know offhand how to start a brand new broker node. Is this
>>     something that will be obvious if i read the documentation, or is
>>     there any trick to it?
>> Just start another instance of Rabbit.
> Err, well you need to set some environment variables, at least 
> RABBITMQ_NODENAME and RABBITMQ_CONFIG_FILE. You'd probably also want 
> to set tcp_listeners to [] in the config for the temporary 
> shovel-hosting broker (otherwise it will try to open 5672 and fail).
> See http://www.rabbitmq.com/clustering.html#single-machine

This all makes sense. I am fairly new to RabbitMQ, but i'm impressed by 
the documentation so far.

> (although you will not be forming the nodes into a cluster, it still 
> applies).

The broker i am shovelling from and to, which is on the same machine, is 
part of a cluster (we have two brokers clustered, for HA). Does that 
make any difference?



Tom Anderson | Developer | +44 20 7826 4312 | timgroup.com 

STATEMENT OF CONFIDENTIALITY: The information contained in this 
electronic message and any attachments to this message are intended for 
the exclusive use of the addressee(s) and may contain confidential or 
privileged information. If you are not the intended recipient, please 
notify Tom Anderson at TIM Group at tom.anderson at timgroup.com and 
destroy all copies of this message and any attachments.

TIM Group is the trading name for YouDevise Limited. YouDevise Limited 
is registered in England, No. 3331176. Registered office: 3 Copthall 
Avenue, London, EC2R 7BH.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130703/1383e000/attachment.htm>

More information about the rabbitmq-discuss mailing list