because you didn't include them upfront... suonayi came up with valid solution, but with missing details, it wasn't clear what your requirements were.
back to the story... why don't you just have a camel route that listens for a "delete user" message and then uses JMX to remove the queue in question? your system manager app can send the "delete user" message with the user to remove to the queue the camel route is listening on. On Thu, Oct 17, 2013 at 8:11 AM, HellKnight <hellkni...@foxmail.com> wrote: > The login process is something like our forum , loginName and password > is > sent to some web service, the web service verify these data from what's > stored in database of server side.If loginName and password is legal, the > client program will receive an OK message and a consumer is created , > starting to receive ActiveMQ messages. > if user is offline, I want to keep messages for him as long as possible > , > until the end of solar system will be the best, haha. Actually We don't > want > to tolerate any message loss. > If that user is deleted by some system manager , his queue will be > deleted from broker. > Just out of curiosity, I think what I need should be some message > routing > mechanism inside broker when a message will be copied to multiple > destinations , why you wanted me to offer these seemingly irrelavant info ? > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Is-it-possible-to-dispatch-a-message-in-the-topic-to-only-a-certain-queues-while-using-virtual-topic-tp4672622p4672947.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta
