Maybe some more information; Here's a recent local logging 14:37:17,865 DEBUG [org.apache.activemq.transport.failover.FailoverTransport] (Periodic Recovery) Stopped tcp://localhost:61616 14:37:17,866 DEBUG [org.apache.activemq.transport.failover.FailoverTransport] (Periodic Recovery) Reconnect was triggered but transport is not started yet. Wait for start to connect the transport. 14:37:17,866 DEBUG [org.apache.activemq.transport.failover.FailoverTransport] (Periodic Recovery) Started unconnected 14:37:17,866 DEBUG [org.apache.activemq.transport.failover.FailoverTransport] (Periodic Recovery) Waking up reconnect task 14:37:17,867 DEBUG [org.apache.activemq.transport.failover.FailoverTransport] (ActiveMQ Task-1) urlList connectionList:[tcp://localhost:61616], from: [tcp://localhost:61616] 14:37:17,867 DEBUG [org.apache.activemq.transport.failover.FailoverTransport] (ActiveMQ Task-1) Attempting 0th connect to: tcp://localhost:61616 14:37:17,867 DEBUG [org.apache.activemq.transport.failover.FailoverTransport] (ActiveMQ Task-1) Connection established 14:37:17,868 INFO [org.apache.activemq.transport.failover.FailoverTransport] (ActiveMQ Task-1) Successfully connected to tcp://localhost:61616
On 13/12/2019, 18:13, "rdvries" <robbert.devr...@triodos.com.INVALID> wrote: Hi all! We've recently been connecting to another party's broker, with a failover setup. We soon discovered we're getting a lot of these: 11:51:36,115 INFO [org.apache.activemq.transport.failover.FailoverTransport] (ActiveMQ Task-1) Successfully connected to tcp://<host>:61616 Sometimes even a couple per second. It seems to be related to the failover. I can reproduce this by just running a local broker with a failover URL like so (no messaging involved) <resource-adapter id="activemq-ra"> <archive> activemq-rar.rar </archive> <config-property name="ServerUrl"> failover:(tcp://localhost:61616,tcp://localhost:61617)?randomize=false </config-property> <connection-definitions> <connection-definition class-name="org.apache.activemq.ra.ActiveMQManagedConnectionFactory" jndi-name="activemq/ConnectionFactory" pool-name="activemq"> <recovery no-recovery="true"/> </connection-definition> </connection-definitions> </resource-adapter> Using version 5.15.9, with Jboss 7.2. Locally, the message / (re?)connection seems to be triggered by the periodic recovery period of the transaction manager. So setting the tx manager recovery like following, I can locally exactly see the 30/10 pattern in the loggings: -DRecoveryEnvironmentBean.periodicRecoveryPeriod=30 -DRecoveryEnvironmentBean.recoveryBackoffPeriod=10 We've been tinkering and staring at trace/debug logging for too long now... time to ask help :) -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html