I see a bunch of these messages in the logs of Node-2 : 2017-11-13 15:30:06,506 | INFO | Establishing network connection from vm://SecondaryBroker?create=false&async=false to tcp://x.x.x.x:61616 | org.apache.activemq.network.DiscoveryNetworkConnector | ActiveMQ Task-4 2017-11-13 15:37:49,129 | INFO | ActiveMQ.Advisory.MasterBroker Inactive for longer than 1800000 ms - removing ... | org.apache.activemq.broker.region.Topic | ActiveMQ Broker[SecondaryBroker] Scheduler 2017-11-13 15:38:37,095 | WARN | Network connection between vm://SecondaryBroker#16 and tcp://x.x.x.x/x.x.x.x:61616@46009 shutdown due to a remote error: java.util.concurrent.TimeoutException | org.apache.activemq.network.DemandForwardingBridgeSupport | triggerStartAsyncNetworkBridgeCreation: remoteBroker=tcp://x.x.x.x/x.x.x.x:61616@46009, localBroker= vm://SecondaryBroker#16 2017-11-13 15:38:37,101 | INFO | Connector vm://SecondaryBroker stopped | org.apache.activemq.broker.TransportConnector | ActiveMQ BrokerService[SecondaryBroker] Task-21 2017-11-13 15:38:37,102 | INFO | SecondaryBroker bridge to Unknown stopped | org.apache.activemq.network.DemandForwardingBridgeSupport | ActiveMQ BrokerService[SecondaryBroker] Task-21 2017-11-13 15:38:38,101 | INFO | Establishing network connection from vm://SecondaryBroker?create=false&async=false to tcp://x.x.x.x:61616 | org.apache.activemq.network.DiscoveryNetworkConnector | ActiveMQ Task-5 2017-11-13 15:38:38,102 | INFO | Connector vm://SecondaryBroker started | org.apache.activemq.broker.TransportConnector | ActiveMQ Task-5 2017-11-13 15:39:08,169 | WARN | Network connection between vm://SecondaryBroker#20 and tcp://x.x.x.x/x.x.x.x:61616@46010 shutdown due to a remote error: java.util.concurrent.TimeoutException | org.apache.activemq.network.DemandForwardingBridgeSupport | triggerStartAsyncNetworkBridgeCreation: remoteBroker=tcp://x.x.x.x/x.x.x.x:61616@46010, localBroker= vm://SecondaryBroker#20 2017-11-13 15:39:08,171 | INFO | Connector vm://SecondaryBroker stopped | org.apache.activemq.broker.TransportConnector | ActiveMQ BrokerService[SecondaryBroker] Task-25 2017-11-13 15:39:08,171 | INFO | SecondaryBroker bridge to Unknown stopped | org.apache.activemq.network.DemandForwardingBridgeSupport | ActiveMQ BrokerService[SecondaryBroker] Task-25
I could only understand second statement in the logs above. How do I indicate to the broker that network connector should not be timed out? Can I increase the maxInactivityDuration of the transport connector to a large value in both brokers? What is the reason for other logs? I couldn't see anything relevant in the logs of Node-1 during this time. -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
