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

Using failover: with static discovery in a network connector to choose from a master/slave tuple leads to hangs and invalid states

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

      Description

      static discovery will try to connect to all provided urls. When the list is a master/slave pair with shared storage, only one will active, leading log messages indicating repeated failure to connect.
      A potential solution is to use failover: just to pick a url but let it delegate failover to the network connector such that the network bridge is correctly stopped/restarted.
      static:(failover:(tcp://a:61616,tcp://slave:61616)?maxReconnectAttempts=..)
      This does not work reliably atm, due to inconsistency in the failover reconnect logic, a network connectors interest in transport interruption/resumption and the lack of thread safety in tracking existing bridges.

        Attachments

        Issue Links

          Activity

            People

            • Assignee:
              gtully Gary Tully
              Reporter:
              gtully Gary Tully

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment