do take the other good advice :-) but for your existing use case: be sure and delete any temp destination; javax.jms.TemporaryQueue#delete when you are done b/c the lifecycle is tied to the connection that created it. If you disable advisories then u need to tell a connection to not watch advisories - connection factory.watchTopicAdvisories=false and it will ask the broker about the temp dest.
On 10 October 2013 05:11, javaG <zenma...@gmail.com> wrote: > > In my application, I use request-reply by creating temp queue and creating a > new replyConsumer for each message to use replyConsumer.poll() method to get > reply back. After getting reply I close the replyConsumer. Messaging works > fine but each time a message is sent a topic > ActiveMQ.Advisory.Consumer.Queue.ID:xxxxxxxxxxxxxx is created and remains > there. So if millions of messages are sent millions of rows will be created > in the ActiveMQ web console for topics. I tried to disable advisories > message to solve this problem but then request-reply does not work anymore > as it throws exceptions like Cannot publish to a deleted destination. So I > am stuck. Any one has a solution? > > Thanks > > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Too-many-advisories-topics-created-in-ActiveMQ-tp4672501.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- http://redhat.com http://blog.garytully.com
