Mailing-List: contact uima-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: uima-user@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of eaepstein@gmail.com
 designates 209.85.146.176 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=amR4r0pd83L1bB5lklQC9phtIreRPMunDwXtGJks5kZ+3pc6pMBaveHwczS9rhXFGX
         nlR8d2nPi+OrGdStOh2//Gz+Z5A6YiU9AiCR+WlMO42QRLKWv+PqBJCZHRVhBse8bmqv
         TJ8MG0fceDaFS9ZqVHDhbfevthKeXv8AYyIm0=
Message-ID: <cd6edfd30811140711h2e8984cdy14f35c65a8745414@mail.gmail.com>
Date: Fri, 14 Nov 2008 10:11:20 -0500
From: "Eddie Epstein" <eaepstein@gmail.com>
To: uima-user@incubator.apache.org
Subject: Re: undeployAsyncService?
In-Reply-To: <491C8F34.7010206@cs.cmu.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <491C8F34.7010206@cs.cmu.edu>

Hi Eric,

UIMA AS service queues on ActiveMQ are actually
created either by a service registering as a consumer
or by a client registering as a producer; these queues
are persistent. Service reply queues use the JMS
temporary queue mechanism, and these go away
as soon as the consumer connection is broken.

One approach would be to use the JMX service
for the AMQ broker which reports the number of active
consumers for each queue. Not sure how reliable
this mechanism is for the 4.1.1 broker we are using.

The other way to go would be as you suggest, killing
the service and then using client timeouts to detect
that the service is not there.

Eddie

On Thu, Nov 13, 2008 at 3:33 PM, Eric Riebling <er1k@cs.cmu.edu> wrote:
> I have a strange use case which requires taking down as well
> as starting up remote services.  Is there a mechanism which
> allows removal, or de-registration of a service with a
> particular broker?  My only idea on how to achieve this is
> to kill the service process brute force, and let the broker "figure
> out" that the service has gone away, I'm assuming by way of
> a timeout, or a getMeta failure.
>
> Any ideas?  Is there a way to tell a broker directly to stop
> using a particular service, once it's been deployed?
>
> Thanks,
>
> -er
> --
> Eric Riebling  NSH 4623,  LTI,   SCS,  CMU
> 412.268.9872   http://www.cs.cmu.edu/~er1k
>