I can confirm that you'll need that for propagation of destinations. On Sep 4, 2013, at 8:43 AM, Gary Tully <gary.tu...@gmail.com> wrote:
> just a thought, I recall an issue with the destination filter, can't > recall the exact detail but it may help for the server 5.8 case. > mod the clients networkConnector to add: > > <networkConnector ... , > destinationFilter="Legacy,ActiveMQ.Advisory.Consumer.>,ActiveMQ.Advisory.Consumer.Queue.>" > ... > > enabling trace=true on the transportConnector or networkConnector url > and trace level logging will let you see the ConsumerInfo for the > advisory consumer, in which you can see the > value of the ConsumerInfo and the corresponding filter. > > On 29 August 2013 08:54, rena <renato.guig...@fastinnovation.it> wrote: >> Thank you christian. >> >> Unfortunately, i have at least 100 client and upgrade all together require >> too much time. >> >> My problem could be resolved using some particular configuration or i have >> no hope? >> >> >> >> -- >> View this message in context: >> http://activemq.2283324.n4.nabble.com/AMQ-5-4-5-8-network-broker-tp4670813p4670892.html >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > > > -- > http://redhat.com > http://blog.garytully.com
