activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-5129) Substitute TimeTask with ScheduledExecutorService in org.apache.activemq.thread.Scheduler
Date Fri, 01 Jun 2018 12:12:00 GMT

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

Gary Tully commented on AMQ-5129:
---------------------------------

it may still be no harm to introduce the scheduled executor even with a pool of one. It would
ensure the thread stays alive but with the changes in AMQ-6979 it is less likely.

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

Mime
View raw message