activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erkan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AMQ-3031) Time Synchronization Solution
Date Fri, 12 Nov 2010 12:27:24 GMT

     [ https://issues.apache.org/activemq/browse/AMQ-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Erkan updated AMQ-3031:
-----------------------

    Component/s: Broker

> Time Synchronization Solution
> -----------------------------
>
>                 Key: AMQ-3031
>                 URL: https://issues.apache.org/activemq/browse/AMQ-3031
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.4.1
>            Reporter: Erkan
>             Fix For: 5.5.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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message