[
https://issues.apache.org/jira/browse/ARTEMIS-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16435643#comment-16435643
]
ASF GitHub Bot commented on ARTEMIS-1803:
-----------------------------------------
Github user michaelandrepearce commented on the issue:
https://github.com/apache/activemq-artemis/pull/2012
As noted my biggest concern is that message refs need to be as light as
humanly possible as they’re all in memory and affects greatly the scaling.
I would personally prefer the refactor if needed, than take this hit.
Especially as this is only needed by someone wanting to use this in a
plugin. Which means everyone else has to suffer
> 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)
