activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] [Commented] (AMQ-6808) Preserve destination when browsing scheduled messages
Date Tue, 12 Sep 2017 20:19:00 GMT


Timothy Bish commented on AMQ-6808:

The ActiveMQ message already has a field that could be used for this, called original destination.
 You could modify the code to apply the destination from the Message to setOriginalDestination
prior to calling the setDestination with the ReplyTo value of the management request.   

> Preserve destination when browsing scheduled messages
> -----------------------------------------------------
>                 Key: AMQ-6808
>                 URL:
>             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

View raw message