[ https://issues.apache.org/jira/browse/ARTEMIS-4707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Bertram updated ARTEMIS-4707: ------------------------------------ Description: A primary broker using replication for HA may connect and disconnect from a backup lots of times during its life-span. The {{boolean}} returned by {{org.apache.activemq.artemis.core.replication.ReplicationManager#isSynchronizing}} is never reset to account for this. Once the primary synchronizes *once* with a backup the returned {{boolean}} will always be {{{}false{}}}. Furthermore, it is always {{true}} once the replication manager is created - even before it is started and actually enters into the synchronization phase. (was: A primary broker may connect and disconnect from a backup lots of times during its life-span. The {{boolean}} returned by {{org.apache.activemq.artemis.core.replication.ReplicationManager#isSynchronizing}} is never reset to account for this. Once the primary synchronizes *once* with a backup the returned {{boolean}} will always be {{{}false{}}}. Furthermore, it is always {{true}} once the replication manager is created - even before it is started and actually enters into the synchronization phase.) > Synchronizing status of ReplicationManager not up-to-date > --------------------------------------------------------- > > Key: ARTEMIS-4707 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4707 > Project: ActiveMQ Artemis > Issue Type: Bug > Reporter: Justin Bertram > Assignee: Justin Bertram > Priority: Major > > A primary broker using replication for HA may connect and disconnect from a > backup lots of times during its life-span. The {{boolean}} returned by > {{org.apache.activemq.artemis.core.replication.ReplicationManager#isSynchronizing}} > is never reset to account for this. Once the primary synchronizes *once* > with a backup the returned {{boolean}} will always be {{{}false{}}}. > Furthermore, it is always {{true}} once the replication manager is created - > even before it is started and actually enters into the synchronization phase. -- This message was sent by Atlassian Jira (v8.20.10#820010)