activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-6808) Preserve destination when browsing scheduled messages
Date Fri, 15 Sep 2017 13:15:00 GMT

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

ASF subversion and git services commented on AMQ-6808:
------------------------------------------------------

Commit e1699d58c899700a221662d6f4c728cc306ee97b in activemq's branch refs/heads/activemq-5.15.x
from [~erik.wramner]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=e1699d5 ]

AMQ-6808 preserve destination for browsed scheduled messages

(cherry picked from commit c691124d3288ffc9299bedca69b952952f2cbcf6)


> 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)

Mime
View raw message