Mailing-List: contact activemq-users-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: activemq-users@geronimo.apache.org
Received-SPF: pass (herse.apache.org: domain of lists@nabble.com designates
 72.21.53.35 as permitted sender)
Message-ID: <8527141.post@talk.nabble.com>
Date: Tue, 23 Jan 2007 10:12:11 -0800 (PST)
From: "tim.geldart" <tim.geldart@inovis.com>
To: activemq-users@geronimo.apache.org
Subject: Re: Stomp durable topic do not UNSUB
In-Reply-To: <ec6e67fd0701220929w1e204ebamf7006619c6260b6d@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <8458129.post@talk.nabble.com>
 <ec6e67fd0701220929w1e204ebamf7006619c6260b6d@mail.gmail.com>


I appreciate the feedback. However, the following comments raise additional
questions:


James.Strachan wrote:
> 
> So to stop collecting messages for durable subscriptions, you need to
> delete the subscription via the MBeans - i.e. its an adminstrative
> issue (rather than via stomp/jms).
> 
> If you want to start/stop subscriptions within a client, then don't
> use durable topics, use non-persistent subscriptions
> 

1. When I use the distribution's example to create a durable subscription,
then modify ConsumerTool.java to call session.unsubscribe() immediately
prior to session.close(), the JMX console shows the subscription as deleted
after executing "ant consumer". This appears to be identical behavior to
deleting the subscription via MBeans (and is not what a stomp UNSUB does..
even after applying AMQ-1077).

Would one be mistaken to expect stomp client behavior to be consistent with
openwire client behavior?

2. After manually deleting a durable subscription, the broker appears to
continue "remembering" published messages, even if there are no active
subscriptions to receive the messages. If no other subscriptions are
subsequently created, then continued publishing of messages to the
unsubscribed topic will eventually use 100% of the memoryManager's
configured memory (in my case, 200 MB), after which point, the only way to
recover is to bounce the broker.

Should one expect the manual deletion of a durable subscription to yield the
same behavior as if the subscription never existed? Otherwise, the only
adminstrative option to ridding the system of an unwanted subscription
appears to involve bouncing the broker.

-Tim


-- 
View this message in context: http://www.nabble.com/Stomp-durable-topic-do-not-UNSUB-tf3042823.html#a8527141
Sent from the ActiveMQ - User mailing list archive at Nabble.com.