Home/ Questions/Q 7983421
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-04T10:57:12+00:00

I am using ActiveMQ version 5.4 and I have a pure master slave configuration

  • 0

I am using ActiveMQ version 5.4 and I have a pure master slave configuration. My slave is configured such that starts its network transports connectors in the event of a failure. My clients are configured using the failover protocol, just like the docs say:

failover://(tcp://masterhost:61616,tcp://slavehost:61616)?randomize=false

When my master dies, the clients successfully fail over to the slave perfectly. The problem is that after I recover (i.e. stop the slave, copy over the data, restart the master, then restart the slave), the clients are still trying to connect to the the slave (which does not have any open network connectors at that point). Thus, the clients never reconnect to the master after restarting it. Is this how it’s supposed to work?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I’ve seen this as well. If you’re using the PooledConnectionFactory, set an expiry timeout on the pooled connections via setExpiryTimeout. The API documentation here suggests that this will force reconnection to the master broker:

    allow connections to expire, irrespective of load or idle time. This is useful with failover to force a reconnect from the pool, to reestablish load balancing or use of the master post recovery

    • 0