[
https://issues.apache.org/jira/browse/QPID-6557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14559507#comment-14559507
]
Robbie Gemmell commented on QPID-6557:
--------------------------------------
I can't really comment to the behaviour itself, but on the spec...the field is
defined as <field name="correlation-id" type="*" requires="message-id"/> at
http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-messaging-v1.0-os.html#type-properties
There are 4 types in the spec which 'provide message-id':
http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-messaging-v1.0-os.html#type-message-id-ulong
http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-messaging-v1.0-os.html#type-message-id-uuid
http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-messaging-v1.0-os.html#type-message-id-binary
http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-messaging-v1.0-os.html#type-message-id-string
> number not accepted for correlation-id
> --------------------------------------
>
> Key: QPID-6557
> URL: https://issues.apache.org/jira/browse/QPID-6557
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: 0.32
> Reporter: Matt Broadstone
> Priority: Minor
>
> The AMQP 1.0 specification isn't exactly clear on what a "correlation-id" is,
> and therefore specifies "*" as its type. Most of the qpid tools hide this
> behind the api and coerce values to strings for you, however recently when
> interacting with a qpid broker I discovered that sending an integer value for
> the correlation-id results in qpidd dropping the value, and replacing it with
> a null value when replying on a queue/topic specified in the reply-to
> property.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
