Re: WOTimer and Servlet Deploy
Re: WOTimer and Servlet Deploy
- Subject: Re: WOTimer and Servlet Deploy
- From: email@hidden
- Date: Tue, 20 Dec 2005 09:02:39 +1300
Hello Helge;
Timing in this situation is very much non-critical –– I just need it
to fire sometime in the approximate time specified. However my
observation is that under servet deploy, the WOTimer does not appear
to be firing at all. I would use java's own Timer mechanism, but I'd
rather not change the code if there's something simple I am missing.
cheers.
I do not know what you are trying to do with the Timer, but if this
Timer
needs to be precise and fire on a very regular basis, and it is not
the only
Timer, I would not reccomend using it and instead using custom made
Threads
instead. I found out that as soon as you get more than one Timer
they do not
operate in parallel, but rather sequential. This brings the whole
machine to
a stop if there are many timers running around.
As a consequence it is more a "suggestion of time to fire" than a
real timer
(this precise countdown-thing) what you define if you use a
WOTimer. Seems
as if the "time-to-fire" is not checked very often or at least has
no high
priority.
___
Andrew Lindesay
www.lindesay.co.nz
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden