[ https://issues.apache.org/jira/browse/ARTEMIS-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15818654#comment-15818654 ]
ASF GitHub Bot commented on ARTEMIS-915: ---------------------------------------- GitHub user gaohoward opened a pull request: https://github.com/apache/activemq-artemis/pull/956 ARTEMIS-915 WebComponent stopped when backup failback You can merge this pull request into a Git repository by running: $ git pull https://github.com/gaohoward/activemq-artemis master-915 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-artemis/pull/956.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 #956 ---- ---- > WebComponent stopped when backup failback > ----------------------------------------- > > Key: ARTEMIS-915 > URL: https://issues.apache.org/jira/browse/ARTEMIS-915 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker > Affects Versions: 1.5.1 > Reporter: Howard Gao > Assignee: Howard Gao > Fix For: 1.5.next > > > In a fail-back scenario, if live is shut down and restart again, the backup > will stop itself, and so will its webcomponent, which is a web server > embedded. In that case user will not be able to access the backup via the web > interface. > So no matter whether the backup server is becoming live or fail back, the web > component should be available all the time, until the VM is shutdown. -- This message was sent by Atlassian JIRA (v6.3.4#6332)