Uploaded image for project: 'ActiveMQ Artemis'
  1. ActiveMQ Artemis
  2. ARTEMIS-2531

FederatedQueue has invalid filter string leading to an infinite consumer loop

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.10.1
    • 2.11.0
    • Broker
    • None

    Description

      FederatedQueue by default is supposed to set a metadataFilter to will exclude reacting to federated consumers so a loop isn't created. Unfortunately the filter does not work because there is a hyphen in the key name so it gets ignored. The name of the key used is federation-name . The key property needs to be prefixed with "hyphenated_props:" in the expression for the filter to work. Currently an infinite loop and consumers will be rapidly created until crashing the broker unless the filter is fixed (if using by directional federated queues). The other option is to change key name but this works too.

      The following documentation describes hyphens in filter expressions: https://activemq.apache.org/components/artemis/documentation/latest/filter-expressions.html

      From the docs:

      The JMS spec also states that property identifiers (and therefore the identifiers which are valid for use in a filter expression) are an, "unlimited-length sequence of letters and digits, the first of which must be a letter. A letter is any character for which the method Character.isJavaLetter returns true. This includes _ and $. A letter or digit is any character for which the method Character.isJavaLetterOrDigit returns true." This constraint means that hyphens (i.e. -) cannot be used. However, this constraint can be overcome by using the hyphenated_props: prefix. For example, if a message had the foo-bar property set to 0 then the filter expression hyphenated_props:foo-bar = 0 would match it.

      Attachments

        Issue Links

          Activity

            People

              cshannon Christopher L. Shannon
              cshannon Christopher L. Shannon
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 3h 10m
                  3h 10m