Hi James, Thanks for the response,
> > > > The Destination object doesn't disappear but you will be unable to > > send messages to it after the client which created it disappears (once > > the broker detects its gone). > > > > Whats the need of keeping it there if it cannot be used again. > > We're not keeping it there :). > > The Destination objects are like URL classes; they can be attached to > messages or held in client's RAM - the broker can't really go around > every JVM and make sure they don't happen to have a reference to a non > existent destination lying around > > > > there will only mitigate the broker's resources. > > The broker resources have been removed when the client disconnected. > > > > How could be this temporary > > destination be removed (somewhere it was suggested to use purge(), but I > > could not find any such function in the openwire cpp APIs I m using.) > > They are removed automatically when a client disconnects. > > This FAQ entry might help you understand that a Destination is not the > same thing as a broker's resources for queues.... > > http://incubator.apache.org/activemq/how-do-i-create-new-destinations.html > I went through the link and found it useful to understand my issues well. Thanks and Regards Navin -- View this message in context: http://www.nabble.com/How-to-create-a-temporary-Queue-tf2145190.html#a5942024 Sent from the ActiveMQ - Dev forum at Nabble.com.
