You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Matt Pavlovich (Jira)" <ji...@apache.org> on 2023/01/06 00:19:00 UTC

[jira] [Commented] (AMQ-9188) Track jobs scheduled and dispatched

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

Matt Pavlovich commented on AMQ-9188:
-------------------------------------

Why the whole message as payload?

I think this should probably be an advisory with only metadata such as -- message id and destination. Some people abuse scheduled messages and this would create a lot of traffic on advisory topics which is ill-advised.

Sending the whole message payload could be handled with more flexibility as an interceptor, virtual topic sub, other pub-sub type approach where there is just another interested subscriber to the scheduled messages

> Track jobs scheduled and dispatched
> -----------------------------------
>
>                 Key: AMQ-9188
>                 URL: https://issues.apache.org/jira/browse/AMQ-9188
>             Project: ActiveMQ
>          Issue Type: New Feature
>          Components: Broker
>    Affects Versions: 5.18.0
>            Reporter: Max
>            Priority: Minor
>              Labels: features
>
> Augment scheduler to forward scheduled and dispatched messages to a destination, if such is configured.
> e.g.
> <broker ... schedulerSupport="true" schedulerActivityDestination="topic://ActiveMQ.Scheduler.Activity" >
> If schedulerActivityDestination is not set, current behavior is unaffected.
> Otherwise...
> When message is successfully scheduled scheduler should set property AMQ_SCHEDULER_ACTIVITY to SCHEDULED and forward scheduled message to the schedulerActivityDestination
> When message is successfully dispatched scheduler should set property AMQ_SCHEDULER_ACTIVITY to DISPATCHED and forward scheduled message to the schedulerActivityDestination



--
This message was sent by Atlassian Jira
(v8.20.10#820010)