|
From: Leif M. <le...@ta...> - 2004-09-28 04:00:24
|
Jeffrey,
I am unclear on the nature of the "event" that you have scheduled?
Is this a part
of your Java application?
The Wrapper itself does not do anything with the system clock or
control how the
JVM process sees the system clock. No matter what the value of the
use_system_time
property is, the JVM should see the system time exactly as if it was
running standalone.
The use_system_time property is used to control how the Wrapper
process itself
handles timing internally. By setting it to false, it uses internal
"ticks" which is not as
accurate as the system time, but is much more resilient to high system
loads and changes
in system time. Neither method is directly visible to the Java
application. The tick
method simply makes the Wrapper much more stable under load and makes it
very
unlikely that a JVM will be restarted due to such loads.
If you want to see what time the Wrapper thinks it is as you change the
time. Set the
wrapper.debug=true property and then watch the wrapper.log file across
the system
time change.
Cheers,
Leif
Jeffrey R. Ostrowski wrote:
>I"m using v.3.1.1. I've set use_system_time=FALSE in
>my .conf file. When I change my computer settings between
>EDT and EST (and vice versa), there is no apparent change
>when my event runs. For example, if I have an event
>scheduled for 2:58PM and the clock changes from 3:57PM EDT
>to 2:57PM EST on my machine, the event is not triggered at
>the new time of 2:58PM.
>
>Is there a parameter that I'm missing???
>
>
|