[
https://issues.apache.org/jira/browse/ARTEMIS-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15820082#comment-15820082
]
ASF GitHub Bot commented on ARTEMIS-915:
----------------------------------------
Github user clebertsuconic commented on a diff in the pull request:
https://github.com/apache/activemq-artemis/pull/956#discussion_r95721658
--- Diff:
artemis-web/src/main/java/org/apache/activemq/artemis/component/WebServerComponent.java
---
@@ -170,4 +173,15 @@ private WebAppContext deployWar(String url, String
warFile, Path warDirectory) t
handlers.addHandler(webapp);
return webapp;
}
+
+ @Override
+ public void stop() throws Exception {
--- End diff --
@gaohoward if someone called stop() directly, I would expect it to really
shutdown.
But I guess it's ok this way.
> 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)
