[
https://issues.apache.org/jira/browse/QPID-7085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15156854#comment-15156854
]
Rob Godfrey commented on QPID-7085:
-----------------------------------
yes - this is a hang-over from the old JMX API. One issue is that the AMQP /
JMS message-id cannot (reasonably) be guaranteed to be unique within the
broker, does not have a consistent format between AMQP versions, and is also
optional and so may not even be present:-(. As such the message number has
always been used through management APIs, but unfortunately has always been
labelled as the message "id". I agree the argument would more properly be
called message number - but that would be an API change (actually it might best
be described as the broker-message-id, versus the amqp-message-id... there are
potentially other message identifiers as well).
> [Java Broker] messageId is used inconsistently
> ----------------------------------------------
>
> Key: QPID-7085
> URL: https://issues.apache.org/jira/browse/QPID-7085
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: qpid-java-6.0
> Reporter: Lorenz Quack
>
> A message has two semantically similar sounding attributes:
> * messageId
> * Message Number
> In the web UI when looking at a message both are displayed.
> The REST API (e.g., Queue#getMessageContent()) has one parameter "messageId"
> but in fact requires the mssage number.
> This is confusing/misleading.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
