[jira] [Resolved] (ARTEMIS-4188) creating dynamicQueues from an JavaEE MDB applies configured messageSelector as per-queue filters

["Justin Bertram (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARTEMIS-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Bertram resolved ARTEMIS-4188.
-------------------------------------
    Fix Version/s: 2.29.0
         Assignee: Justin Bertram
       Resolution: Fixed

> creating dynamicQueues from an JavaEE MDB applies configured messageSelector as per-queue filters
> -------------------------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-4188
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4188
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 2.19.1
>            Reporter: Wizz
>            Assignee: Justin Bertram
>            Priority: Major
>             Fix For: 2.29.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> h3. Steps to reproduce:
> h4. Configuration
> # Configure wildfly activemq-ra 
> # Create MDB Consumer with following ActivationSpec
> {code:java}
> @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}'"
>                 )
>         }
> )
> {code}
> # Deploy the service
> h4. Expected Result
> # (/) MyQueue created
> # (x) Queue-Attribute 'filter' is empty
> # (/) Consumer is attached to queue with messageSelector as consumer filter
> h4. Actual Result
> # (/) MyQueue created
> # (!) Queue-Attribute 'filter' contains messageSelector
> # (/) Consumer is attached to queue with messageSelector as consumer filter
> h3. 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.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)