activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Shannon <christopher.l.shan...@gmail.com>
Subject Re: Configuring Virtual Destinations via Jolokia REST Api in ActiveMQ 5.13.2
Date Fri, 18 Mar 2016 14:10:52 GMT
You can create a Jira for a feature request and if someone has time they
can look at it.  Contributions are also always welcome so if you have time
you could take a look at creating a pull request to add the feature.  If
you were going to take a look at implementing it I would probably start
with using the JavaRuntimeConfigurationPlugin and wrapping that to do the
work under the covers.

On Fri, Mar 18, 2016 at 10:06 AM, Adel Boutros <sta191919@gmail.com> wrote:

> Hello guys,
>
> There seem to be many possible ways of doing it. However, it seems a bit
> complex when you compare it to the way it is done in Qpid Java Broker or
> ActiveMQ Artemis for example:
>
>
>    - Qpid Java broker:
> http://localhost:8080/api/latest/binding/topic/queue
>    (+json request file for filters)
>    - Artemis: http://localhost:8161/jolokia/exec/
>    org.apache.activemq.artemis:type=Broker,brokerName="localhost"
>    ,module=Core,serviceType=Server/createDivert/myDivert/topic/queue
>
> Whereas in ActiveMQ, I have to integrate Camel, customize stuff, etc...
>
> This makes me wonder if there is a reason there is no native support for
> that in ActiveMQ's broker knowing that it also has support for Jolokia REST
> just like Artemis
>
> Regards,
>
> Adel Boutros
> Murex SAS
> www.murex.com
>
> On Fri, Mar 18, 2016 at 2:50 PM, Quinn Stevenson <
> quinn@pronoia-solutions.com> wrote:
>
> > Sorry - I was a little vague.
> >
> > I’d use a Camel route that called a bean to determine the recipient list.
> > That bean would load it’s configuration from a file, DB or whatever you
> > requirements are.  The bean would also be able to update it’s
> configuration
> > when the file changed.  You could use another route in the broker polling
> > for a configuration file, and then update the beans config when you got a
> > new file.
> >
> > I didn’t work through all the details, but that’s what I was thinking.
> >
> > > On Mar 18, 2016, at 7:09 AM, Tim Bain <tbain@alumni.duke.edu> wrote:
> > >
> > > In non-embedded Camel, it's possible to define routes at runtime via
> the
> > > Java API; see for example
> > >
> >
> http://nigap.blogspot.com/2012/02/camel-create-routes-dynamically.html?m=1
> > >
> > > I'm not sure if it would work for an embedded Camel context, but it
> > might.
> > >
> > > Tim
> > > On Mar 17, 2016 5:45 PM, "Quinn Stevenson" <
> quinn@pronoia-solutions.com>
> > > wrote:
> > >
> > >> Yes - the Camel route would be static, but you could use the recipient
> > >> list EIP to dynamically determine where the messages are sent.
> > >> http://camel.apache.org/recipient-list.html <
> > >> http://camel.apache.org/recipient-list.html>
> > >>
> > >>> On Mar 17, 2016, at 5:15 PM, Adel Boutros <sta191919@gmail.com>
> wrote:
> > >>>
> > >>> Hello Quinn,
> > >>>
> > >>> Camel route is still a static way of doing it as I have to write it
> in
> > >> Xml
> > >>> file. It doesn't suite my test case which requires "dynamic" route
> > >> creation
> > >>> while the broker is running. Do you confirm this? Unless I have
> missed
> > >>> something.
> > >>>
> > >>> Just to compare with Artemis, for example, via Jolokia, you can
> create
> > a
> > >>> "Divert" which redirects messages from Topic to Queue via a REST call
> > to
> > >>> the running broker. The same applies to Qpid Java broker.
> > >>>
> > >>> Regards,
> > >>> Adel Boutros
> > >>> Murex SAS
> > >>> www.murex.com
> > >>>
> > >>> On Thu, Mar 17, 2016 at 1:33 AM, Quinn Stevenson <
> > >>> quinn@pronoia-solutions.com> wrote:
> > >>>
> > >>>> You may be able to accomplish what you’re after using a Camel
route
> > >>>> embedded in the ActiveMQ broker.
> > >>>> http://activemq.apache.org/broker-camel-component.html <
> > >>>> http://activemq.apache.org/broker-camel-component.html>
> > >>>>> On Mar 16, 2016, at 4:06 PM, Adel Boutros <sta191919@gmail.com>
> > wrote:
> > >>>>>
> > >>>>> Hello Christopher,
> > >>>>>
> > >>>>> In the way we will be using the broker, we would provide an
API for
> > >>>> clients
> > >>>>> to create these "redirections" between queues and topics on
the
> fly.
> > So
> > >>>>> this feature would be really useful as I know no other way
of
> > linking a
> > >>>>> queue to a topic.
> > >>>>>
> > >>>>> Regards,
> > >>>>> Adel Boutros
> > >>>>> Murex SAS
> > >>>>> www.murex.com
> > >>>>>
> > >>>>> On Wed, Mar 16, 2016 at 7:51 PM, Christopher Shannon <
> > >>>>> christopher.l.shannon@gmail.com> wrote:
> > >>>>>
> > >>>>>> Currently this doesn't exist because Virtual destinations
can only
> > be
> > >>>> set
> > >>>>>> on start up or modified by a runtime plugin. (either the
xml
> runtime
> > >>>> plugin
> > >>>>>> or the new java based one added in 5.13.0)
> > >>>>>>
> > >>>>>> There would need to be a new feature implemented to enable
> > >> modification
> > >>>>>> through JMX.
> > >>>>>>
> > >>>>>> On Wed, Mar 16, 2016 at 1:45 PM, Adel Boutros <
> sta191919@gmail.com>
> > >>>> wrote:
> > >>>>>>
> > >>>>>>> Hello,
> > >>>>>>>
> > >>>>>>> I was wondering if there is a way to configure a Virtual
> > Destination
> > >>>>>>> programmatically using the Jolokia REST Api?
> > >>>>>>>
> > >>>>>>> I explored the JMX module using JConsole but found
no possible
> > >>>> solution.
> > >>>>>>>
> > >>>>>>> I am following the example here:
> > >>>>>>> http://activemq.apache.org/virtual-destinations.html
> > >>>>>>>
> > >>>>>>> Regards,
> > >>>>>>>
> > >>>>>>> Adel Boutros
> > >>>>>>> Murex SAS
> > >>>>>>> www.murex.com
> > >>>>>>>
> > >>>>>>
> > >>>>
> > >>>>
> > >>
> > >>
> >
> >
>

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