So what do you want to happen when the Version2 consumer isn't connected? Right now the Version2 messages stay available for the Version2 when it reconnects; what do you want to happen instead?
On Mon, Nov 17, 2014 at 12:00 PM, juanmanuel.romeraferrio < juanmanuel.romerafer...@gmail.com> wrote: > Hi, > > I'm in a trouble in my system. I have a lot of clients that send message > with differente VERSION and I have one consumer per version that recibe > this > message, I'm using message selector on a only queue to do that, but I found > a problem when I sent for exmple message of 2 versions and I had only one > consumer up, the message that are of the version of consumer up, are not > consumed and still like pending. > > I found a link that describe that > http://trenaman.blogspot.co.uk/2009/01/message-selectors-and-activemq.html > > Then I saw the idea of Composite Destinations, this works, but this has a > limitation. When I need add a new consumer I need change the activemq.xml > of > broker, and this mean stop and start the broker. > > What's is the best solution? > > Thanks, > Juan Manuel > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Message-Selector-or-Composite-Destinations-tp4687564.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
