Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
2.5.0
-
None
-
None
Description
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.
Attachments
Issue Links
- links to
