ActiveMQ Artemis：在故障转移后从站作为主站重新启动后，从属服务器重新启动后，控制台(从属服务器(不会启动。在日志中，我可以看到hawtio服务被破坏。谁能说出为什么在奴隶身上摧毁了hawtio服务？这是正确的行为吗？如果没有，我怎样才能阻止它被摧毁？
阿尔忒弥斯版本：2.5.0
原木：
Apache ActiveMQ Artemis Backup Server version 2.5.0 [null] started, waiting
live to fail before it gets active
AMQ221024: Backup server ActiveMQServerImpl::serverUUID=2dd29ee1-2ce9-11e8-
a95e-0050568c47be is synchronized with live-server.
AMQ221031: backup announced
Keycloak integration is disabled
Initiating quorum vote: LiveFailoverQuorumVote
Waiting 30 seconds for quorum vote results.
AMQ221060: Sending quorum vote request to
stomvjms11.xz.xyz.com/10.21.46.44:8003: ServerConnectVote
[nodeId=2dd29ee1-2ce9-11e8-a95e-0050568c47be, vote=false]
AMQ221061: Received quorum vote response from
AMQ221070: Restarting as backup based on quorum vote results.
[io.hawt.web.AuthenticationFilter] Destroying hawtio authentication filter
[io.hawt.HawtioContextListener] Destroying hawtio services
[org.apache.activemq.hawtio.plugin.PluginContextListener] Destroyed artemis-
plugin plugin
[org.apache.activemq.hawtio.branding.PluginContextListener] Destroyed
activemq-branding plugin
[org.apache.activemq.artemis.core.server] AMQ221002: Apache ActiveMQ Artemis
Message Broker version 2.5.0 [2dd29ee1-2ce9-11e8-a95e-0050568c47be] stopped,
uptime 4 minutes
[org.apache.activemq.artemis.core.server] AMQ221000: backup Message Broker
is starting with configuration Broker Configuration
您看到的行为是一个错误。它最初是在ARTEMIS-1737中报道的。它在Artemis 2.5.0中修复。