[
https://issues.apache.org/jira/browse/AMQ-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13748034#comment-13748034
]
Gary Tully commented on AMQ-4682:
---------------------------------
modification to virtualDestinations add, modify, remove implemented. Changes
are effective on the next destination add (new consumer) which gates concurrent
access.{code}<destinationInterceptors>
<virtualDestinationInterceptor>
<virtualDestinations>
<virtualTopic name="B.>" selectorAware="false"/>
</virtualDestinations>
</virtualDestinationInterceptor>
</destinationInterceptors>{code}
virtualDestinationInterceptor are a little odd b/c virtualTopics are enabled by
default w/o any explicit config. On an initial add, the existing default
interceptor, if present, is modified.
> runtime configuration - allow selective application of changes to xml
> configuration without broker restart
> ----------------------------------------------------------------------------------------------------------
>
> Key: AMQ-4682
> URL: https://issues.apache.org/jira/browse/AMQ-4682
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker
> Affects Versions: 5.8.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Labels: configuration, runtime, updates
> Fix For: 5.9.0
>
>
> support on the fly configuration changes where appropriate.
> Via JMX it is possible to make changes but they don't persist.
> Via osgi we can restart the broker to pick up changes to xml config
> but where it makes sense, we should be able to apply changes on the fly.
> A first example would be the addition on a new network connector by
> the addition of the relevant xml config (edit or copy over) that is
> in use by the broker.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
