[AMQ-6808] Preserve destination when browsing scheduled messages

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 5.15.1, 5.16.0
• Component/s: Job Scheduler
• Assignee: Timothy A. Bish
• Reporter: Erik Wramner
• Created: 12/Sep/17 19:05
• Updated: 15/Sep/17 13:16
• Resolved: 15/Sep/17 13:16

Description

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.

Issue Links

• links to: GitHub Pull Request #259