[
https://issues.apache.org/jira/browse/QPID-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16411729#comment-16411729
]
Rob Godfrey commented on QPID-8139:
-----------------------------------
[~alex.rufous]: the draft JMS AMQP mapping specifies how JMSMessageID should be
sent over AMQP - I think what we need to do in the broker is use a slightly
modified implementation of the JMS selector code when the consumer is using the
AMQP 1.0 protocol so that it recognizes the rules defined in the mapping
> [Broker-J] Selector containing JMSMessageID expressions might not find the
> message when expression JMSMessageID value starts with 'ID:' prefix but the
> real message id does not include the prefix
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-8139
> URL: https://issues.apache.org/jira/browse/QPID-8139
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
> Affects Versions: qpid-java-broker-7.0.2
> Reporter: Alex Rudyy
> Priority: Major
>
> JMS specification requires JMSMessageID value to start with prefix "ID:". The
> JMS client might add the prefix "ID:" to the values not starting from "ID:"
> in order to be JMS compliment. If the altered JMSMessageID value is used to
> build a selector expression like "JMSMEssageID='ID:<real id>'", the target
> message might not be found as Broker-J uses real message ids in message
> lookup.
> Potentially, filtering functionality for JMSMEssageID expression can be
> enhanced to detect the cases when the "ID:" prefix is specified in the
> selector but not included into the real message id value and find the correct
> message.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
