hmm, that is an interesting use case, a concentrator. At the moment all destinations are global so the will map one to one across the network.
I don' think there is a way to configure a concentrator out of the box but all of the component bits are there so you should be able to make it work with a bit of customisation. You would need to have the client forwarding bridge contain a statically included composite destination, using a comma separated list of client q destinations. This will subscribe to and shunt all of the messages from client q's to the server side, however the target destination will need to be replaced to implement the concentrator. On the server side, you will need a broker plugin that intercepts the send operation and maps the X client q destinations to the shared q. An alternative approach would be to implement the mapping in the client broker (in configuration) via virtual destinations, so you configure all of the client destinations to internally forward to a shared queue and then propagate just that shared queue through the network. If there is no value in the client queue destinations, you could put in a broker plugin on the client that replaces the destinations at that point an be done with it. So you have a few options, depending on your exact use case, the plugin architecture gives you complete control really. On 9 May 2011 10:18, GuyPardon <[email protected]> wrote: > Thanks, > > Follow-up question: assuming there are many client queues: is it possible to > setup this 'forwarding' mechanism between brokers so that many client queues > are 'forwarding' to a single, shared server-side queue? > > Guy > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Using-queue-to-support-disconnected-clients-tp3505304p3508760.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- http://blog.garytully.com http://fusesource.com
