activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARTEMIS-1803) MessageReference should include sessionId
Date Thu, 12 Apr 2018 13:47:00 GMT

    [ https://issues.apache.org/jira/browse/ARTEMIS-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16435570#comment-16435570
] 

ASF GitHub Bot commented on ARTEMIS-1803:
-----------------------------------------

Github user cshannon commented on the issue:

    https://github.com/apache/activemq-artemis/pull/2012
  
    Furthermore there is more to a broker than just processing.  Monitoring and metrics are
very important to business flows and trying to save a few bytes of memory is not worth it
if you sacrifice basic things such as being able to do proper logging and troubleshooting.


> 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)

Mime
View raw message