Christopher L. Shannon commented on AMQ-5129:

While I don't disagree that the scheduler could be looked at it to modernize a 
bit and maybe switch to using ScheduledExecutorService, I would recommend that 
you try a newer version of the broker as well to see if it helps your issue.  
If the timer tasks are suddenly not working then there's probably some other 
underlying issue going on that is the root cause which might have already been 
fixed in a newer version.  The newest version is 5.14.0 and there have been 
1966 commits since 5.9.1 so quite a lot has changed since 5.9.1 was released.

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

Reply via email to