As Rob pointed out, there are several solutions to this, the simplest one being as in the old joke, Dr, it hurts when I do this. - Don't do it?
You could achieve the same thing with one queue and selectors - *which could run CPU up* You could use a temp queue per processing unit and handle a lot of messages (This is nice for pub/sub) You could use one queue and a bit of instanceof code (It looks a bit crufty but it is very functional) On Oct 9, 2013, at 11:05 PM, Robert Davies <rajdav...@gmail.com> wrote: > What you have described is a bit of an anti-pattern - there's some guidelines > here in the faq: > http://activemq.apache.org/how-should-i-implement-request-response-with-jms.html > Its an anti-pattern because there is a lot of broker side over head with > creating temporary destinations and consumers (as you are seeing). > However, for your case you probably need to enable GC on destinations - see > http://activemq.apache.org/delete-inactive-destinations.html > > On 10 Oct 2013, at 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. >
