hi all,
i have an engine runs on weblogic at a unix machine. in my engine i have a timer and the timer writes to the log every 1 minute. but my log looks like that;
INFO 2007-03-05 15:49:41,626 aa.bb.cc.MyEngine - one minute passed...
INFO 2007-03-05 15:50:59,786 aa.bb.cc.MyEngine - one minute passed...
INFO 2007-03-05 15:52:18,414 aa.bb.cc.MyEngine - one minute passed...
INFO 2007-03-05 15:53:36,846 aa.bb.cc.MyEngine - one minute passed...
INFO 2007-03-05 15:54:55,473 aa.bb.cc.MyEngine - one minute passed...
INFO 2007-03-05 15:56:14,135 aa.bb.cc.MyEngine - one minute passed...
INFO 2007-03-05 15:57:32,463 aa.bb.cc.MyEngine - one minute passed...
why the difference between 2 log statements doesnt equal 60 second, equals about 80 second?
my code like that;
private int secondCount = 0;
private int timerCount = 0;
private Timer timer = null;
.....
public void sendData() {
timer = new Timer();
timer.schedule(new RemindTask(), 0, 100);
while (notFalse) {
...
}
...
timer.cancel();
}
class RemindTask extends TimerTask {
public void run() {
timerCount++;
if (timerCount > 9) { ////// when 1 second passed
timerCount = 0;
...
secondCount++;
if (secondCount>59) { ///////////// when 1 minute passed
secondCount = 0;
logger.info("one minute passed...");
...
}
}
}
thanks in advance...
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
The next execution of the run () method will be done after the 1st execution is over. The first execution need not take 0 milliseconds - it might take a few milliseconds or seconds depending upon what you do, so that duration will get added before the next run () execution happens. If you are using some logging component for logging this to a file, then it will have its own overhead. If it is multi-threaded, then even more.
Firstly I agree with sciuriware comment, you should be firing a task every minute and doing you logging in there. If you have other regular tasks that u want done at varying times then create extra tasks instead of trying to manage everything in a single task. You'll get better accuracy and a lot cleaner code.
Also from the Timer javadoc:
> This class does not offer real-time guarantees: it schedules tasks using the Object.wait(long) method.
and from scedule:
> Subsequent executions take place at approximately regular intervals, separated by the specified period.
So you shouldn't expect it to be perfect. If you need better accuracy than it offers then you'll need to use a different method.
For precision scheduler you can try opensymphony quartz scheduler.
It is free and very poverful.
http://www.opensymphony.co
http://www-128.ibm.com/dev
i created 2 timers, first one is fired 100 milisecond, and if timercounter>99 i write the screen (it means, i get every 10 second), the other's interval time is 10 second. out is like that;
myTimer2 Tue Mar 06 09:31:19 GMT 2007
myTimer2 Tue Mar 06 09:31:29 GMT 2007
myTimer1 Tue Mar 06 09:31:29 GMT 2007
myTimer2 Tue Mar 06 09:31:39 GMT 2007
myTimer1 Tue Mar 06 09:31:40 GMT 2007
myTimer2 Tue Mar 06 09:31:49 GMT 2007
myTimer1 Tue Mar 06 09:31:51 GMT 2007
myTimer2 Tue Mar 06 09:31:59 GMT 2007
myTimer1 Tue Mar 06 09:32:02 GMT 2007
myTimer2 Tue Mar 06 09:32:09 GMT 2007
myTimer1 Tue Mar 06 09:32:12 GMT 2007
myTimer2 Tue Mar 06 09:32:19 GMT 2007
myTimer1 Tue Mar 06 09:32:23 GMT 2007
myTimer2 Tue Mar 06 09:32:29 GMT 2007
myTimer1 Tue Mar 06 09:32:34 GMT 2007
myTimer2 Tue Mar 06 09:32:39 GMT 2007
myTimer1 Tue Mar 06 09:32:44 GMT 2007
myTimer2 Tue Mar 06 09:32:49 GMT 2007
myTimer1 Tue Mar 06 09:32:55 GMT 2007
i dont understand why the second one works fine, but the first one that i compute doesnt work properly. my logic is very simple, just increase the timercount and if it bigger than 99 set zero.
it seems not important but some crital situations and when interval time gets bigger, it becomes more important. for example, at my first post above, when i try to cathc 60 second, i got 80 second.
as i know timer cant be prevent and when its time comes, it starts execution. why this mechanizm different in java? is it a priority problem? and is there any mechanizm runs like timer but guarantees working accurately.
Business Accounts
Answer for Membership
by: sciuriwarePosted on 2007-03-05 at 07:07:20ID: 18654697
Your own fault: set the timer to an interval of 60000 milliseconds
and drop your own counting.
;JOOP!