Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-4144

Address Setting redeliveryCollisionAvoidanceFactor cannot be specified as a float number

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • None
    • AMQ 7.7.0.OPR.2.GA, AMQ 7.8.0.dev
    • operator
    • False
    • False
    • ?
    • Hide
      Previously, if you added an address settings configuration to the Custom Resource (CR) instance for a broker deployment (that is, by adding an `addressSettings.addressSetting` section), you could not include the `redeliveryCollisionAvoidanceFactor` property. If you included this property and specified a value, the Operator failed to process the CR. This issue is now resolved.
      Show
      Previously, if you added an address settings configuration to the Custom Resource (CR) instance for a broker deployment (that is, by adding an `addressSettings.addressSetting` section), you could not include the `redeliveryCollisionAvoidanceFactor` property. If you included this property and specified a value, the Operator failed to process the CR. This issue is now resolved.
    • Documented as Resolved Issue
    • Verified in a release
    • Hide

      Add the entries below in the example CR:

        addressSettings:
    addressSetting:
    - match: testRedeliveryCollisionAvoidanceFactor
      redeliveryCollisionAvoidanceFactor: 0.3

      Then apply the CR using: 

      oc apply -f the CR_example_file.yml
      Show
      Add the entries below in the example CR: addressSettings: addressSetting: - match: testRedeliveryCollisionAvoidanceFactor redeliveryCollisionAvoidanceFactor: 0.3 Then apply the CR using:  oc apply -f the CR_example_file.yml

    Description

      Based on artemis documentation: https://activemq.apache.org/components/artemis/documentation/latest/undelivered-messages.html

      the collision-avoidance-factor setting must be a float between 0 and 1:

      The redelivery-delay can be also be modified by configuring the redelivery-collision-avoidance-factor. This factor will be made either positive or negative at random to control whether the ultimate value will increase or decrease the redelivery-delay. Then it's multiplied by a random number between 0.0 and 1.0. This result is then multiplied by the redelivery-delay and then added to the redelivery-delay to arrive at the final value.

      When I tried to specify it as 0.3 in the CR, CR apply fails with:

      The ActiveMQArtemis "ex-aao" is invalid: spec.addressSettings.addressSetting.redeliveryCollisionAvoidanceFactor: Invalid value: "string": spec.addressSettings.addressSetting.redeliveryCollisionAvoidanceFactor in body must be of type number: "string"

      Attachments

        Activity

          People

            rhn-support-rkieley Roderick Kieley
            tbueno@redhat.com Tiago Bueno
            Tiago Bueno Tiago Bueno
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: