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

Log a warning when starting a networkConnector with static:failover without using maxReconnectAttempts=0

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Abandoned
    • 5.0.0
    • AGING_TO_DIE
    • Broker

    Description

      When configuring a networkConnector using the static:failover: transport, you'll be unable to failover if you don't specify the maxReconnectAttempts=0 option on the failover transport.

      We periodically see users on the mailing list getting tripped up by this, since it's not intuitive or obvious. One option would be to simply refuse to start the broker when this happens (since there probably isn't a valid reason to configure a networkConnector that way), but since that's probably too draconian, we should instead log a warning that tells the user that this is probably not what they want so they can fix it.

      Attachments

        Activity

          People

            mattrpav Matt Pavlovich
            tbain98 Tim Bain
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: