Uploaded image for project: 'ActiveMQ'
  1. ActiveMQ
  2. AMQ-6124

failover backup transports do not update the brokerInfo leaving stale org.apache.activemq.ActiveMQConnection#getBrokerName

    XMLWordPrintableJSON

    Details

      Description

      with broker url

      failover:(tcp://a:<port>,tcp://b:<port> ")?randomize=false&priorityBackup=true

      The brokerName as reported by
      org.apache.activemq.ActiveMQConnection#getBrokerName stays at A even after failover to B.

      The backup transport are started up front and the brokerInfo is not cached so it never gets replayed to the jms connection.

      The same is true for the backup attribute

        Attachments

          Activity

            People

            • Assignee:
              gtully Gary Tully
              Reporter:
              gtully Gary Tully
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: