[
https://issues.apache.org/jira/browse/AMQ-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13112945#comment-13112945
]
Timothy Bish commented on AMQ-3031:
-----------------------------------
It seems like a simple solution would be to remove the 'executePeriodically'
function and just have the 'schedualPeriodically' called for all scheduled
tasks as that uses fixed-delay execution instead of fixed-rate which is prone
to stacking when tasks are delayed or in the reporters case the clock is
changed.
> Time Synchronization Solution
> -----------------------------
>
> Key: AMQ-3031
> URL: https://issues.apache.org/jira/browse/AMQ-3031
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.4.1
> Reporter: Erkan
> Priority: Critical
> Fix For: 5.6.0
>
> Attachments: Scheduler-ActivemqCore.java, Scheduler-KahaDB.java
>
>
> We had a Problem if we synchronize the time of 1.1.2000 to the actual date.
> The cpu load increase to 170% over a long time period. We analyse the problem
> and find out that is a java timer problem. We pass the classes Scheduler.java
> in following packages:
> 1. \kahadb\src\main\java\org\apache\kahadb\util
> 2. activemq-core\src\main\java\org\apache\activemq\thread
> We change the TimerTask by ScheduledThreadPoolExecutor. That was the
> solution. I want to discuss if that is the right solution or not. Can you
> analyze the classes and say if that is the right way or not? If not can you
> propose a solution. If yes can you release that with the next version.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
