With a forwarding bridge in-place between a remote collector and the central server, a queue that is created on the collector will not automatically be reflected/created on the server. You either have to define a queue in the server broker's cfg file or have clients, which are connected to the server broker, create the queue.
Define one queue (e.g., Server.Q) on the server broker that is used by all collectors to forward messages to those consumers that are connected to the server broker and reading from that particular queue. So in essence, Server.Q is the logical communications channel between the producers on the collectors and consumers on the central server. Joe Tamir wrote: > > I'm new to ActiveMQ, so bear with me ... > > I want to use ActiveMQ in the following scenario, and haven't find a way > to configure it the way I want it. > I have a lot of remove JVM (let's call them collectors) that send data to > one central JVM (server). > > For scalability and availability reasons, I want to embed a broker into > every collector and have one main broker on the server. So far so good. > I saw that there's a feature called Store-and-Forward and I thought that > would be perfect for my needs, but it seems like in Store-and-Forward > every Q I'll define on a collector would be reflected on the server, so > I'll end up with multiple queues on the server. That's not what I want. > I want all the data from all the collector Q's to get forwarded into a > single main queue on the server broker. Of course I want the framework to > do it for me, so I'll benefit all the cool features it has to offer. > > Can this be achieved using ActiveMQ? > -- View this message in context: http://www.nabble.com/ActiveMQ-topology-question-%28Store-and-Forward%29-tp15179713s2354p15183421.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
