Hello, I have this scenario: 2 broker active configured in cluster, a client c++ tha is connected to the brokers using failover protocol. The options in activemq.xml on brokers side are:
<transportConnector name="openwire" uri="tcp://0.0.0.0:61616?maximumConnections=1000&wireFormat.maxFrameSize=104857600&wireFormat.maxInactivityDuration=500&wireFormat.maxInactivityInitialDelay=100" discoveryUri="multicast://default"/> while on client side option are: failover:(tcp://HOST1:61616,tcp://HOST2:61616)?initialReconnectDelay=10&maxReconnectDelay=100&randomize=true&wireFormat.maxInactivityDuration=500&wireFormat.maxInactivityDurationInitalDelay=100 in order to use InactivityMonitor when connection to broker is lost. Using this configuration when broker on HOST1 is killed then client switch on broker on HOST2 and vice versa. If broker1 and broker2 are running and broker1 is disconnected (knock off LAN) then client connect to broker2 after a delay of 10-15 seconds and not immediately, the connection to broker1 is down immediately using InactivityMonitor but the reconnection has a delay. There is a way in orde to reduce delay on reconnection to second broker? There are errors on configuration showed? Thank you. bye Domenico. -- View this message in context: http://activemq.2283324.n4.nabble.com/failover-broker-reconnection-delay-tp4716461.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
