Hello.
I would propose using the Dynamic Shovel in RabbitMQ. With shovels you can control who initiates the TCP session, so you can have B connect to A and shovel messages from a queue on B to an exchange or queue on A. You can even have the shovel on queuemanager C and have it connect to both A and B and shovel in any direction, but that’s another story.
/Fredrik
--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
rabbitmq-user...@googlegroups.com.
To post to this group, send email to
rabbitm...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the Google Groups "rabbitmq-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/rabbitmq-users/YRNP8PnRH1E/unsubscribe.
To unsubscribe from this group and all its topics, send an email to rabbitmq-user...@googlegroups.com.
Is this still the best way to solve this problem? We are looking at a similar situation and want to know if dynamic shovel is still state of the art for rabbit.
--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.