[jira] [Commented] (AMQ-4682) runtime configuration - allow selective application of changes to xml configuration without broker restart
[ https://issues.apache.org/jira/browse/AMQ-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13834910#comment-13834910 ] Gary Tully commented on AMQ-4682: - @tamilmaran - not at the moment. Please open an enhancement jira for that with some detail on the supporting use case, will see to get it done for 5.10 > 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 was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (AMQ-4682) runtime configuration - allow selective application of changes to xml configuration without broker restart
[ https://issues.apache.org/jira/browse/AMQ-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13834800#comment-13834800 ] Tamilmaran commented on AMQ-4682: - By using this configuration can we change the port of transport connector or add a new transport connector? > 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 was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (AMQ-4682) runtime configuration - allow selective application of changes to xml configuration without broker restart
[ https://issues.apache.org/jira/browse/AMQ-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756537#comment-13756537 ] Gary Tully commented on AMQ-4682: - property replacement is there, system properties and the properties file locations from PropertyPlaceholderConfigurer > 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
[jira] [Commented] (AMQ-4682) runtime configuration - allow selective application of changes to xml configuration without broker restart
[
https://issues.apache.org/jira/browse/AMQ-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13751778#comment-13751778
]
Gary Tully commented on AMQ-4682:
-
support for modifications to primitive attributes of destinationPolicy{code}
...
{code}
> 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
[jira] [Commented] (AMQ-4682) runtime configuration - allow selective application of changes to xml configuration without broker restart
[
https://issues.apache.org/jira/browse/AMQ-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13751238#comment-13751238
]
Gary Tully commented on AMQ-4682:
-
support modification to authorizationPlugin map - add/remove/mod
authorizationEntry {code}
...{code}
> 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
[jira] [Commented] (AMQ-4682) runtime configuration - allow selective application of changes to xml configuration without broker restart
[ https://issues.apache.org/jira/browse/AMQ-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13748041#comment-13748041 ] Gary Tully commented on AMQ-4682: - if (the default value), an update can be forced via JMX. The *updateNow* operation on the service=RuntimeConfiguration,name=Plugin Mbean will force the application of any changes to the xml configuration. > 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
[jira] [Commented] (AMQ-4682) runtime configuration - allow selective application of changes to xml configuration without broker restart
[
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}
{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
[jira] [Commented] (AMQ-4682) runtime configuration - allow selective application of changes to xml configuration without broker restart
[
https://issues.apache.org/jira/browse/AMQ-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13743916#comment-13743916
]
Gary Tully commented on AMQ-4682:
-
support for mods/updates to networkconnctors is complete, with an xml config
like:{code}
http://activemq.apache.org/schema/core"; start="false" ... >
...{code}
Any modification to the networkConnectors element will be picked up within a
second (checkPeriod).
> 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
