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

creating dynamicQueues from an JavaEE MDB applies configured messageSelector as per-queue filters

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.19.1
    • 2.29.0
    • None
    • None

    Description

      Steps to reproduce:

      Configuration

      1. Configure wildfly activemq-ra
      2. Create MDB Consumer with following ActivationSpec
        @MessageDriven(
                activationConfig = {
                        @ActivationConfigProperty(
                                propertyName = "destinationLookup",
                                propertyValue = "java:global/federation/artemis/dynamicQueues/MyQueue"
                        ),
                        @ActivationConfigProperty(
                                propertyName = "destinationType",
                                propertyValue = "javax.jms.Queue"
                        ),
                        @ActivationConfigProperty(
                                propertyName = "maxSession",
                                propertyValue = "1"
                        ),
                        @ActivationConfigProperty(
                                propertyName = "messageSelector",
                                propertyValue = "HeaderField = '${my.system.property.value}'"
                        )
                }
        )
        
      3. Deploy the service

      Expected Result

      1. MyQueue created
      2. Queue-Attribute 'filter' is empty
      3. Consumer is attached to queue with messageSelector as consumer filter

      Actual Result

      1. MyQueue created
      2. Queue-Attribute 'filter' contains messageSelector
      3. Consumer is attached to queue with messageSelector as consumer filter

      Effects

      On a multi server-group setup (same service deployed to several server groups) the queue filter is set to HeaderField = '${my.system.property.value}' with 'my.system.property.value' of the first server group.

      Thus messages of the other server group will not be accepted by the queue.

      Attachments

        Issue Links

          Activity

            People

              jbertram Justin Bertram
              wizz Wizz
              Votes:
              0 Vote for this issue
              Watchers:
              3 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 - 10m
                  10m