Re: [Wrapper-user] Daylight savings time

[Leif M. <le...@ta...>]

Richard,
    Thanks.  I have not seen this particular problem myself.  (No 
daylight savings time
here in Japan :-)  But I was aware of problems like this when the system 
time is
adjusted.

    Now that daylight saving time is passed, this will not be an issue 
for another year.
(The fall adjustment will not result in a restart.  But all timeouts 
will be an extra hour
long during that hour).  The only workaround to this right now is to set 
the cpu and
ping timeouts to values that are over an hour.

    This has been fixed in 3.1.0 if you enable the new Tick based 
timer.   It is disabled
by default until it has received some more testing.  My tests so far all 
give it very high
marks.  So unless any problems are reported from the 3.1.0, it will most 
likely
become the default in the following 3.1.1 release.

    FYI.  The new Tick based timer manager can be enabled in 3.1.0 using the
following property:
wrapper.use_system_time=FALSE

Cheers,
Leif

Richard Emberson wrote:

> found the following in one of our nightly load test logs:
>
> INFO   | wrapper  | 2004/04/04 03:59:59 | Wrapper Process has not 
> received
> any CPU time for 3600 seconds.  Extending timeouts.
> INFO   | jvm 1    | 2004/04/04 03:01:59 | Wrapper Manager: The Wrapper 
> code
> did not ping the JVM for 120 seconds.  Quit and let the Wrapper resynch.
>
> I guess the wrapper does not adjust for daylight savings time
> changes.
>
> Richard