activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pothier, Peter" <ppoth...@CROSSBEAMSYS.COM>
Subject RE: Duplicate Subscriptions activemq-admin query
Date Mon, 26 Apr 2010 13:43:23 GMT
Hi,

A little more information.  The tests that are run Subscribe using
selectors.
I find the Subscriptions list grows when the test client subscribes
using a
different selector (disconnecting and then reconnecting, subscribing
using
the new selector, but the same clientID).  Are there any unexpected side
affects
when a client subscribes at different times for a durable topic using
different
selectors?

Since the list returned by the "activemq-admin query" is growing, my
concern
is that ActiveMQ may not release all references to a message if it
thinks
it has not sent to all destinations.

Peter P

-----Original Message-----
From: Pothier, Peter [mailto:ppothier@CROSSBEAMSYS.COM] 
Sent: Thursday, April 22, 2010 7:43 PM
To: users@activemq.apache.org
Subject: Duplicate Subscriptions activemq-admin query

Hi,

 

Using ActiveMQ 5.3.0, with both libstomp and activemq-cpp clients, and
using

     activemq-admin query

to view details, we have some tests that
connect/disconnect/reconnect/disconnect...

to both a queue and a durable topic.  In between, persistent messages
are sent.

 

The "Subscriptions" value returned by this query script for the durable
topic

seems to grow and grow and grow over time as the clients reconnect

 

     Subscriptions =
[org.apache.activemq:BrokerName=amq-broker,Type=Subscription,persistentM
ode=Durable,

 
subscriptionID=gtest_consumer,destinationType=Topic,destinationName=cons
umer,clientId=gtest_consumer, 

 
org.apache.activemq:BrokerName=amq-broker,Type=Subscription,persistentMo
de=Durable, 

 
subscriptionID=gtest_consumer,destinationType=Topic,destinationName=cons
umer,clientId=gtest_consumer, 

 
org.apache.activemq:BrokerName=amq-broker,Type=Subscription,persistentMo
de=Durable, 

 
subscriptionID=gtest_consumer,destinationType=Topic,destinationName=cons
umer,clientId=gtest_consumer, 

 
org.apache.activemq:BrokerName=amq-broker,Type=Subscription,persistentMo
de=Durable, 

 
subscriptionID=gtest_consumer,destinationType=Topic,destinationName=cons
umer,clientId=gtest_consumer,

     etc.....

 

This does not occur with the Queue, which is also being
connected/disconnected/reconnected...

 

      Subscriptions =
[org.apache.activemq:BrokerName=amq-broker,Type=Subscription,persistentM
ode=Non-Durable,

 
destinationType=Queue,destinationName=producer,clientId=Manager,consumer
Id=0343f653-1ea0-bd02-ee77-8debd69325b9_0_0]

 

which only displays a single subscription.

 

This behavior occurs using both libstomp and activemq-cpp clients.

 

Is this behavior normal for the durable topic?  Any idea why the
duplicate entries?

 

Thanks!

Peter P

 


Mime
View raw message