[ https://issues.apache.org/jira/browse/QPID-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16475434#comment-16475434 ]
ASF subversion and git services commented on QPID-8139: ------------------------------------------------------- Commit 86b31afbc98bbd980c2566d0fd48f72e30fe5c69 in qpid-broker-j's branch refs/heads/master from [~alex.rufous] [ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=86b31af ] QPID-8139: [Broker-J][AMQP 1.0] Make sure that selector filter can handle JMSMessageID and JMSCorrelationID values with prefixes as defined in AMQP JMS mapping specification > [Broker-J] [AMQP1-0] [JMSBINDMAP] JMS selectors using JMSMessageID or > JMSCorrelationID expressed using the AMQP type encoded form values fail to > select target message > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > 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, qpid-java-broker-7.0.0 > Reporter: Alex Rudyy > Assignee: Alex Rudyy > Priority: Major > Attachments: > 0001-QPID-8139-Broker-J-AMQP-1.0-Make-sure-that-selector-.patch, > 0002-QPID-8139-Broker-J-AMQP-1.0-Summport-all-message-for.patch > > > (2018-05-10 - rewritten JIRA title/description) > When using the Qpid JMS AMQP 1.0 Client with Broker-J, if the consumer > specifies a JMS message selectors including a {{JMSMessageID}} or > {{JMSCorrelationID}} predicate, the selector can fail to find the target > message in some circumstances. This occurs when the message producer is > configured to use one of the following {{jms.messageIDPolicy.messageIDType}} > modes: {{UUID}}. {{UUID_STRING}}, {{PREFIXED_UUID_STRING}}. In the default > mode, {{BUILTIN}} the problem does not manifest. > The issue is the Broker-J JMS selector implementation does not understand the > AMQP type encoded forms specified by 3.2.1.1 of the Advanced Message Queuing > Protocol (AMQP) JMS Mapping Version 1.0 [WD9]. > The problem also manifests when the Broker's message conversion feature is in > use. For instance, a message produced by a AMQP 0-10 producer cannot be > selected by an consumer using a Qpid JMS Client 1.0 using a {{JMSMessageID}} > or {{JMSCorrelationID}} predicate. This was originally highlighted by the > following user list post: > http://qpid.2158936.n2.nabble.com/JMSMessageID-differences-in-JMS-0-30-0-and-JMS-AMQP-0-x-6-3-0-clients-td7674019.html > (original text of JIRA preserved below) > 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 compliant. 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org