-
Type:
Bug
-
Status: Done
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: AMQ 7.1.0.GA
-
Fix Version/s: AMQ 7.2.0.GA
-
Component/s: broker-core
-
Labels:
-
Environment:
AMQ 7.1 GA
-
Target Release:
-
Affects:Release Notes
-
Release Notes Text:
-
Release Notes Docs Status:Documented as Resolved Issue
After a network outage, the master brokers shut down automatically.
2018-03-14 13:21:02,882 INFO [org.apache.activemq.artemis.core.server.NetworkHealthCheck] Network is unhealthy, stopping service ActiveMQServerImpl::serverUUID=1e32bc1b-0a76-11e8-a1dc-7cd30ad25fd8
|
It recovered and resumed control a little later:
14/03/2018 13:21:13.937
|
2018-03-14 13:21:13,937 INFO [org.apache.activemq.artemis.core.server] AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=true,journalDirectory=/foo/data/journal,bindingsDirectory=./data/bindings,largeMessagesDirectory=./data/large-messages,pagingDirectory=/foo/data/paging)
|
However, the log shows certain destinations being undeployed, although the configuration file had not changed:
2018-03-14 13:21:17,423 INFO [org.apache.activemq.artemis.core.server] AMQ224076: UnDeploying address foo
|
- is related to
-
ARTEMIS-1747 Loading...