You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Christopher L. Shannon (JIRA)" <ji...@apache.org> on 2015/08/04 16:31:04 UTC

[jira] [Comment Edited] (AMQ-5915) Support dynamically adding Virtual Destinations

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

Christopher L. Shannon edited comment on AMQ-5915 at 8/4/15 2:30 PM:
---------------------------------------------------------------------

I took a closer look and I don't think I could easily implement dynamic virtual destinations in the core without adding a lot of locking overhead where it might not be necessary for someone who doesn't need that feature.  

I think the best thing to do would be to modify or extend the RuntimeConfigurationPlugin to allow programmatic access to modify the configuration.  For example, a method could be added to allow setting new virtual destinations on a virtual destination interceptor.  The plugin could then re-apply the configuration in the exact same way it currently does when the xml changes and all of the work that has been done to handle the read/write locks will be re-used. 

So maybe the scope of this ticket should be changed to simply allow programmatic access for runtime configuration instead of only xml.


was (Author: christopher.l.shannon):
I took a closer look and I don't think I could easily implement dynamic virtual destinations in the core without adding a lot of locking overhead where it not be necessary for someone who doesn't need that feature.  

I think the best thing to do would be to modify or extend the RuntimeConfigurationPlugin to allow programmatic access to modify the configuration.  For example, a method could be added to allow setting new virtual destinations on a virtual destination interceptor.  The plugin could then re-apply the configuration in the exact same way it currently does when the xml changes and all of the work that has been done to handle the read/write locks will be re-used. 

So maybe the scope of this ticket should be changed to simply allow programmatic access for runtime configuration instead of only xml.

> 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)