Description
Steps to reproduce:
Configuration
- Configure wildfly activemq-ra
- 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}'" ) } )
- Deploy the service
Expected Result
- MyQueue created
- Queue-Attribute 'filter' is empty
- Consumer is attached to queue with messageSelector as consumer filter
Actual Result
- MyQueue created
- Queue-Attribute 'filter' contains messageSelector
- 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
- links to