activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeremy Levy <jel...@gmail.com>
Subject Re: Patch to disable all Queues
Date Wed, 01 Jun 2011 17:25:54 GMT
Gary-

Right, exclusive consumer won't work as I still want to have multiple
consumers.

I don't have a requirement to start these consumers after the container is
started, you would have to change the system property and redeploy your app
or restart your container.

I'm not that familiar with using properties via jmx/mbean, I followed a
similar pattern using the system property that other tools like Ehcache and
Terrcotta use for controlling some global functionality.

Jeremy

On Wed, Jun 1, 2011 at 10:38 AM, Gary Tully <gary.tully@gmail.com> wrote:

> interesting, I guess the "exclusive consumer" feature won't cut it as
> you are limited to a single consumer.
>
> How do those consumers eventually get activated, is a restart of the
> container without the property?
>
> Would it make sense to have the property settable via jmx, so an mbean
> on the resource adapter?
>
> On 1 June 2011 14:51, Jeremy Levy <jelevy@gmail.com> wrote:
> > We currently deploy our ActiveMQ enabled Message Driven Beans along with
> our
> > larger application inside of an EAR file.  This ear file is then deployed
> > across multiple application servers.  However we only wanted consumers to
> be
> > active on certain dedicated servers.  I wasn't able to find a solution
> > within ActiveMQ that allows us to globally turn off consumers at
> deployment.
> >  For a while we were tweaking the consumers via JMX but that was
> problematic
> > and could only be done after the consumer was activated and started
> > processing.
> > I built our own activemq-rar-5.4.2.rar with the following modifications:
> > In ActiveMQResourceAdapter.java, public void
> > endpointActivation(MessageEndpointFactory endpointFactory, ActivationSpec
> > activationSpec)
> > Before creating the worker and checking to see if it previously activated
> a
> > quick system property check:
> >
> > if (!Boolean.valueOf(System.getProperty("activemq.endpoints.disabled",
> > "false"))) {...
> >
> > If true, dont' actually enable any queues etc.  I'm not sure this is the
> > best method but it seems to be working.  I've included a patch for the
> 5.4.2
> > branch.  I can prepare one for the trunk if the developers think this
> would
> > be a worthwhile contribution.
> > Jeremy
> > --
> > Jeremy Levy
> >
>
>
>
> --
> http://fusesource.com
> http://blog.garytully.com
>



-- 
Jeremy Levy

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message