Thank you all for the replies. I had looked at so many options and even came across lingo which is abandon-ware now. In my case it is volume based (lots and lots of messages) and not size based and no database transactions involved and I use non-persistent messaging. My application which sends messages is a web application which means when an ajax request is received, a message is sent using request-reply pattern which means ajax request is blocked on server side until message response is received or timeout. Also I have to respond to many different ajax requests which each type of request corresponding to a different producer queue. So i have to recreate temp queue destination/replyconsumer for each message using the same activemq connection/session which is separate from producer connection/session. Since I use replyConsumer.poll(), I have to create temp queue/replyConsumer for each message and close upon message response receipt otherwise message responses can get mixed up even with using correlationID. According to JMS spec consumer.poll() will get the next response coming on the consumer.
-- View this message in context: http://activemq.2283324.n4.nabble.com/Too-many-advisories-topics-created-in-ActiveMQ-tp4672501p4672529.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
