You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "clebert suconic (JIRA)" <ji...@apache.org> on 2018/04/30 17:01:03 UTC

[jira] [Closed] (ARTEMIS-1803) Pass ServerConsumer to messageExpired and messageAcknowledged plugin callbacks

     [ https://issues.apache.org/jira/browse/ARTEMIS-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

clebert suconic closed ARTEMIS-1803.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.5.1

> Pass ServerConsumer to messageExpired and messageAcknowledged plugin callbacks
> ------------------------------------------------------------------------------
>
>                 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
>             Fix For: 2.5.1
>
>
> 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.   This is a problem for plugins implementing messageExpired and messageAcknowledged as they can't get the exact consumer based on just the consumerId.
> To solve this the ServerConsumer object responsible for acknowledging the message or expiring the message should be passed to those callback methods.  If consumer doesn't apply (such as when the broker expires internally or internally moves messages and acks) then the consumer object will be null.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)