[
https://issues.apache.org/jira/browse/AMQ-6808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16164241#comment-16164241
]
Erik Wramner commented on AMQ-6808:
-----------------------------------
That is more intuitive. I have updated the pull request and it has passed
Jenkins.
> Preserve destination when browsing scheduled messages
> -----------------------------------------------------
>
> Key: AMQ-6808
> URL: https://issues.apache.org/jira/browse/AMQ-6808
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Job Scheduler
> Reporter: Erik Wramner
> Priority: Minor
>
> It is possible to browse scheduled messages by sending a message to
> ScheduledMessage.AMQ_SCHEDULER_MANAGEMENT_DESTINATION. Unfortunately (for us)
> the most interesting data is missing. SchedulerBroker#sendScheduledJob
> replaces the original destination from the scheduled message with the
> temporary destination of the client asking for the information. That is
> obviously necessary, but it means we can't figure out the final destination
> for the messages.
> We sometimes have thousands of messages and the broker cluster gets into
> trouble. We want to analyze the problem by checking how many messages there
> are for various destinations when this happens. At present that is difficult
> without changing the (many) posting systems to add headers.
> The solution is simple. Copy the original destination to a JMS property
> (schedulerOriginalDestination for example) before overwriting it. I will
> create a pull request.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
