Mailing-List: contact activemq-users-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: activemq-users@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: domain of chirino@gmail.com designates
 64.233.162.205 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=ddEI/NUrVi5SY4I36KB3Mz4Vo9kCUXvabuRR7YYAEulXCtNCwxm6RDDrNNSLBoTowvA8Mcuplz86pOf5uKHctqLpMKqN6crlZol71uLej2yUKL3JM7elvwEra4fQjHv8GfHct2rfKTOTlwBUcUi0AW5nqeOP8Z5pNpyyKACsB5I=
Message-ID: <af2843cd0605251015p45dbbcf1pf249889cf5a1801@mail.gmail.com>
Date: Thu, 25 May 2006 13:15:58 -0400
From: "Hiram Chirino" <hiram@hiramchirino.com>
Sender: chirino@gmail.com
To: activemq-users@geronimo.apache.org
Subject: Re: Problem with No Subscriber Advisory Topic
In-Reply-To: <4551149.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <4393897.post@talk.nabble.com> <4394011.post@talk.nabble.com>
	 <4516715.post@talk.nabble.com> <4528097.post@talk.nabble.com>
	 <4534733.post@talk.nabble.com> <4542304.post@talk.nabble.com>
	 <af2843cd0605241609y58071223p6a247acf4066fadb@mail.gmail.com>
	 <af2843cd0605241612q6fbfa86bp47ec06299883d634@mail.gmail.com>
	 <4551149.post@talk.nabble.com>

If you don't trust your own counters just use the ConsumerEventSource,
it provides a reliable count for you.  If you want to have some
timeout condition, you could do your own client side timeout.  There
are lots of ways to do this, but a recent idea to help with this is
beanflow, see:
http://servicemix.org/site/beanflow.html
It supports adding simple workflow style timeouts.

On 5/24/06, himmeric <himmeric@vnet.ibm.com> wrote:
>
> Thanks I was considering that, but didn't trust the integrity of my own
> internal counter.  Since shutting down a producer when there are still
> consumers would be very bad.
>
> For now I'm using the command line query tool to check for periodic
> ConsumerCount=3D0.
>
> Maybe a better approach would be to use the ConsumerListener class for an
> internal counter with a periodic sanity check using command line tool to
> make sure I didnt shut down something I hadn't.
>
> This could probably be done with JMX too, but I got lost pretty quickly i=
n
> that (new to jmx).
>
> I opened a feature request here:
> http://issues.apache.org/activemq/browse/AMQ-723
> --
> View this message in context: http://www.nabble.com/Problem+with+No+Subsc=
riber+Advisory+Topic-t1621608.html#a4551149
> Sent from the ActiveMQ - User forum at Nabble.com.
>
>


--=20
Regards,
Hiram