[
https://issues.apache.org/jira/browse/AMQ-9157?focusedWorklogId=823170&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-823170
]
ASF GitHub Bot logged work on AMQ-9157:
---------------------------------------
Author: ASF GitHub Bot
Created on: 03/Nov/22 18:30
Start Date: 03/Nov/22 18:30
Worklog Time Spent: 10m
Work Description: cshannon merged PR #929:
URL: https://github.com/apache/activemq/pull/929
Issue Time Tracking
-------------------
Worklog Id: (was: 823170)
Time Spent: 0.5h (was: 20m)
> Add a new advisory type for dispatched messages
> -----------------------------------------------
>
> Key: AMQ-9157
> URL: https://issues.apache.org/jira/browse/AMQ-9157
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker
> Affects Versions: 5.17.2
> Reporter: Christopher L. Shannon
> Assignee: Christopher L. Shannon
> Priority: Minor
> Fix For: 5.18.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> I have a use case where it would be useful for advisory messages to be
> (optionally) turned on for dispatched messages. There is currently an
> advisory for messages that have been consumed (acknowledged) but not for the
> dispatch before the acknowledge.
> I will be adding a new hook to the broker API to do this so that it follows
> the same pattern as the other advisories such as delivered and consumed
> advisories. The existing methods for pre/post processing dispatch are called
> from the TransportConnection but the advisory logic should be called from the
> subscriptions themselves on dispatch so that things like the connection
> context can be easily passed and to better decide when to call it (such as
> not calling for the Queue NULL_MESSAGE type).
> There will be a new policy entry flag called {{advisoryForDispatched}} that
> will be off by default.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
