[
https://issues.apache.org/jira/browse/QPID-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16492464#comment-16492464
]
Alex Rudyy commented on QPID-8139:
----------------------------------
Keith,
Thanks for reviewing the changes in
[f1ce866|https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=].
I was reactant to change {{MessageTransferHeader}} to return {{Object}} from
{{getMessageId}} and {{getCorrelationId}} as cross-protocol conversion requires
more work in general. For example, 1.0 layer would need to know, that
correlationId can be represented as array of bytes. To be fair, I think it
should be a responsibility of conversion modules to do the conversion of
messageId/correlationId between protocols. I will revert the change in f1ce866
and start over.
> [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
> Fix For: qpid-java-broker-7.1.0
>
> Attachments:
> 0001-QPID-8139-Broker-J-AMQP-1.0-Make-sure-that-selector-.patch
>
>
> 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
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
