[
https://issues.apache.org/jira/browse/QPID-8182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16465947#comment-16465947
]
Keith Wall commented on QPID-8182:
----------------------------------
I find other similar problems:
When publishing with Qpid JMS Client with message id type {{UUID}} and
{{UuidStringMode}} modes and receiving the message with Qpid JMS Client 0-x
over AMQP 0-8..0-91, the received converted message arrives with a message id
short-string without the ID: prefix. In all other cases the client publishes
and receives AMQP 0-8..0-91 with an {{ID:}} prefix. These paths should be made
consistent.
When publishing with Qpid JMS Client 0-x over AMQP 0-8..0-91and receiving with
Qpid JMS Client, the received converted message arrives with a
{{message-id-string}} containing the {{ID:}} prefix following by the {{UUID}}
in stringified form. It would be preferable if a {{message-id-uuid}} were used
if possible. This would maximise compatibility with non-JMS clients (that know
nothing of the ID: prefix) and it more efficient on the wire.
> [Broker-J] [Conversion] Message id fidelity lost when converting from AMQP
> 1.0 to 0-10 when message-id-string carries a ID: prefixed UUID
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-8182
> URL: https://issues.apache.org/jira/browse/QPID-8182
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
> Affects Versions: qpid-java-broker-7.0.0
> Reporter: Keith Wall
> Priority: Major
> Fix For: qpid-java-broker-7.1.0, qpid-java-broker-7.0.4
>
>
> If I publish a message from Qpid JMS Client in {{PREFIXED_UUID_STRING}} mode
> and receive the message using the Qpid JMS Client 0-x over AMQP 0-10, the
> UUID of the message id received does not match the original value generated
> by the client.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
