activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher L. Shannon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-5915) Support dynamically adding Virtual Destinations
Date Tue, 04 Aug 2015 13:58:04 GMT

    [ https://issues.apache.org/jira/browse/AMQ-5915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14653677#comment-14653677
] 

Christopher L. Shannon commented on AMQ-5915:
---------------------------------------------

[~gtully],

The main issue with the RuntimeConfigurationPlugin is that a lot of times I'll configure a
broker just using the BrokerService and not the xml config.   I've been looking at how the
Runtime plugin works to add virtual destinations and I'd probably use a similar strategy that
the plugin uses (ie call reapplyInterceptor()  in AbstractRegion to reapply the virtual destinations)
but I was thinking about adding addVirtualDestination/removeVirtualDestination methods to
BrokerService so I could programmatically modify them without having to use xml config.  What
do you think?



> Support dynamically adding Virtual Destinations
> -----------------------------------------------
>
>                 Key: AMQ-5915
>                 URL: https://issues.apache.org/jira/browse/AMQ-5915
>             Project: ActiveMQ
>          Issue Type: New Feature
>            Reporter: Christopher L. Shannon
>            Assignee: Christopher L. Shannon
>             Fix For: 5.13.0
>
>
> Currently virtual destinations must be added before the broker is started by adding them
to a virtual destination interceptor.  This is because of how the virtual destinations are
processed on broker start up.
> I need to be able to add and remove virtual destinations dynamically after the broker
is already running to support dynamic dataflows.  For example, sometimes I need to temporarily
forward messages from one destination to another (such as a topic to queue) without having
to restart the entire broker and change the configuration.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message