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

InitialReconnectDelay appears to be ignored in Discovery transport URLs

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Not A Problem
    • Affects Version/s: 5.2.0
    • Fix Version/s: 5.2.0
    • Component/s: Transport
    • Labels:
      None
    • Environment:

      Windows XP SP3

      Description

      Using a connection URL of

      discovery:(multicast://default?group=test)?maxReconnectAttempts=13&initialReconnectDelay=1000&useExponentialBackOff=false

      one would expect initial connection attempts to go on for at least 13 seconds (13 reconnect attempts with 1000ms delay between attempts) but in fact the error "No uris available to connect to" returned in less than a second. Changing useExponentialBackOff to true delays a failure report to about 41 seconds, which is 10ms * 2^12, which is what you'd expect with 12 reconnect attempts (13 connect attempts) starting with the default 10ms delay and doubling with every attempt, since 2^0+2^1+2^2+...2^n-1 is approx 2^n. (I guess maxReconnectAttempts should be called maxConnectAttempts, but I'm not opening a bug about that.) Changing maxReconnectAttempts to 12 causes the delay to be about 20 seconds, half of what it is for 13, so that checks out.

      Altogether this points to the initialReconnectDelay parameter being ignored on initial connection attempts. It is supposed to work per http://activemq.apache.org/discovery-transport-reference.html

        Attachments

          Activity

            People

            • Assignee:
              gtully Gary Tully
              Reporter:
              jgro Jeremy Grodberg
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: