[QPID-8139] [Broker-J] [AMQP1-0] [JMSBINDMAP] JMS selectors using JMSMessageID or JMSCorrelationID expressed using the AMQP type encoded form values fail to select target message

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: qpid-java-broker-7.0.2, qpid-java-broker-7.0.0
• Fix Version/s: Future
• Component/s: Broker-J
• Assignee: Alex Rudyy
• Reporter: Alex Rudyy
• Created: 23/Mar/18 15:53
• Updated: 02/Oct/19 19:20

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