Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: softfail (athena.apache.org: transitioning domain of
 zenmatix@gmail.com does not designate 216.139.250.139 as permitted sender)
Date: Wed, 11 Dec 2013 16:28:39 -0800 (PST)
From: javaG <zenmatix@gmail.com>
To: users@activemq.apache.org
Message-ID: <1386808119332-4675430.post@n4.nabble.com>
Subject: Topic Advisories pile up in ActiveMQ
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


I have a stomp client that uses temp queue as reply back destination
('/temp-queue/'+uuid_generated_value) to which I subscribe in stomp client
and then send a message on a fixed queue in which I set the reply-to header
to ('/temp-queue/'+uuid_generated_value).  JMS consumer in Java for the
fixed queue responds with reply. This request reply works fine but the issue
is that ActiveMQ web console shows  topics like  

ActiveMQ.Advisory.Consumer.Queue.ID:MYHOST-51244-1386804544982-4:1:39

that keep piling up each time a message is sent and response received.
memory usage ramps up over time.

If I was using Java JMS client, temp-dest.delete() API after receiving
response takes care of this problem but there is no such API for Stomp.
After I receive response in StomP, I unsubscribe this temp queue. This
removes the consumer but those advisory topics keep piling up.  Any solution
to this problem?


--
View this message in context: http://activemq.2283324.n4.nabble.com/Topic-Advisories-pile-up-in-ActiveMQ-tp4675430.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.