[
https://issues.apache.org/jira/browse/AMQ-5129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16495672#comment-16495672
]
ASF subversion and git services commented on AMQ-5129:
------------------------------------------------------
Commit cdb38b32756d70bf7ae149e994abcccc9adca5ae in activemq's branch
refs/heads/master from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=cdb38b3 ]
AMQ-6979 - use scheduler as trigger task - do heavy lifting via the task runner
executor, take care to trap errors to keep scheduler timer alive AMQ-5129
> Substitute TimeTask with ScheduledExecutorService in
> org.apache.activemq.thread.Scheduler
> -----------------------------------------------------------------------------------------
>
> Key: AMQ-5129
> URL: https://issues.apache.org/jira/browse/AMQ-5129
> Project: ActiveMQ
> Issue Type: Wish
> Affects Versions: 5.9.0
> Reporter: matteo rulli
> Priority: Major
> Attachments: proposed-patch.txt
>
>
> Since Timer has only one execution thread, long-running task can affect other
> scheduled tasks. Besides, runtime exceptions thrown in TimerTasks kill the
> only one running thread, bringing down the entire Scheduler.
> I have the suspect that all this could relate to AMQ-3938: sometimes in very
> busy environments I experience exaclty the same problem: a slow leakeage due
> to temp queues that are not deleted. Since
> org.apache.activemq.broker.region.RegionBroker uses a Scheduler to activate
> the purgeInactiveDestinations, a crashed timer could explain why
> purgeInactiveDestinations stops working.
> I attached a tentative patch to migrate timer to ScheduledExecutorService.
> Hope this helps.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
