[
https://issues.apache.org/jira/browse/ARTEMIS-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16435569#comment-16435569
]
ASF GitHub Bot commented on ARTEMIS-1803:
-----------------------------------------
Github user cshannon commented on the issue:
https://github.com/apache/activemq-artemis/pull/2012
It's not attached to the message. The reference has the information for
which consumer is attached to it. The consumer id is not unique so you need to
have the session Id as well otherwise there is no way to find out which
consumer the reference belongs to so this has to be in memory.
I really don't think it's going to be a big deal to add a reference id.
> MessageReference should include sessionId
> -----------------------------------------
>
> Key: ARTEMIS-1803
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1803
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Affects Versions: 2.5.0
> Reporter: Christopher L. Shannon
> Assignee: Christopher L. Shannon
> Priority: Minor
>
> Right now a MessageReference will track a consumerId (in certain scenarios)
> but the sessionId is not included. This is a problem because consumerIds are
> not unique and are duplicated across sessions. In order to find a unique
> consumer you need the sessionId and consumerId as well.
> A use case for when this is important is when writing custom plugins. Some
> of the callbacks pass a message reference and it would be good to be able to
> figure out which consumer the reference belonged to such as in the
> messageAcknowledged callback.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
