[ https://issues.apache.org/jira/browse/ARTEMIS-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16278788#comment-16278788 ]
ASF GitHub Bot commented on ARTEMIS-1537: ----------------------------------------- GitHub user stanlyDoge opened a pull request: https://github.com/apache/activemq-artemis/pull/1688 ARTEMIS-1537 broker was less strict while reloading configuration You can merge this pull request into a Git repository by running: $ git pull https://github.com/stanlyDoge/activemq-artemis-1 E689 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-artemis/pull/1688.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1688 ---- commit 653b995e3dcda0b026dce4dcf4155d317950faf1 Author: Stanislav Knot <sk...@redhat.com> Date: 2017-12-05T16:01:20Z ARTEMIS-1537 broker was less strict while reloading configuration ---- > Broker is less strict with parsing when reloading config than when parsing it > on startup > ---------------------------------------------------------------------------------------- > > Key: ARTEMIS-1537 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1537 > Project: ActiveMQ Artemis > Issue Type: Bug > Reporter: Stanislav Knot > Priority: Minor > > 1) Start broker with default config. > 2) Edit the <addresses> section in broker.xml with bad element > 3) Save the config and observe successful reload in log. (The new > configuration is applied. Had there be new addresses configured, for example, > they would've been created.) > 4) Finally, stop and start again the broker. Notice that the string blah blah > now causes a failure on startup. -- This message was sent by Atlassian JIRA (v6.4.14#64029)