[ 
https://issues.apache.org/jira/browse/ARTEMIS-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16116206#comment-16116206
 ] 

Jiri Danek commented on ARTEMIS-1314:
-------------------------------------

I tried running the test 
{{...jms.tests.selector.SelectorTest#testJMSCorrelationIDOnSelector}} with 
Core, OpenWIre and AMQP. It did fail for AMQP (with qpid-jms as the JMS 
library) and it passed for the other two protocols.

> Using the message filter with JMSCorrelationID seems not to work
> ----------------------------------------------------------------
>
>                 Key: ARTEMIS-1314
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1314
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 2.1.0
>         Environment: * RHEL 7
> * Java 8
> * Qpid JMS 0.23.0
>            Reporter: Jens Reimann
>
> Creating a consumer with a message filter for the JMS correlation ID seems 
> not to work:
> {code:java}
> consumer = session.createConsumer(destination, "JMSCorrelationID='" + id + 
> "'");
> {code}
> The message consumer never receives the message. However, removing the filter 
> an manually filtering does work:
> {code:java}
> if (id.equals(message.getJMSCorrelationID())) {
>   // do stuff
> }
> {code}
> Also does the correlation ID show up in the list of properties:
> {code}
> JMSType => null
> JMSMessageID => ID:d20ffaba-25f4-497a-80e9-99d58101f589:2:1:1-1
> JMSExpiration => 0
> JMSRedelivered => false
> JMSTimestamp => 1501572098651
> JMSXUserID => null
> JMSXGroupSeq => 0
> JMS_AMQP_ACK_TYPE => null
> JMSDeliveryMode => PERSISTENT
> JMSPriority => 4
> JMSReplyTo => null
> JMSXGroupID => null
> JMSDestination => serviceAExternal
> JMSXDeliveryCount => 1
> JMSCorrelationID => d1c2daf6-2f2a-4641-a917-0f211e53e110
> JMSDeliveryTime => 1501572098651
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to