Re: [Wrapper-user] Wrapper and Time

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

Grant,
    :-/  That doesn't surprise me in the least that you are having 
problems there.  The
Wrapper makes extensive use of time both in its native and Java 
components to keep
track of various timeouts.   The Wrapper currently relies on the system 
time being
fairly reliable.

    I could probably add some code to reset the various timeouts in the 
event that either
component of the Wrapper detects that the system time appears to have 
been changed.
Ie when the time decreases or is increased by a large amount.

    Small forward adjustments of the system time would be very difficult 
to detect
because the Wrapper contains features to detect when the system has been 
heavily
loaded.  I am not sure that it would be possible to differentiate 
between the cases where
the process is not given any CPU for a minute vs the clock being 
instantly set ahead
by a minute.

    Could you describe how you are adjusting the time?  Ie by how much, 
in which
direction and why?  It will help me to prioritize this.   If you know 
that the Wrapper
simply does not like having the clock changed, would it be unreasonable 
to just not
do this? Or is changing the clock a common operation?

    I know I can make the Wrapper behave better than it is now, but am 
unsure of how
perfect I can make it perform under all situations.

Cheers,
Leif

Grant (ProtectionNET) wrote:

> Hi,
>  
> I have a case where the Java app changes the system time (via OS calls 
> etc) and when Wrapper is running, I have sometimes seen strange 
> problems and the wrapper service shuts down or goes crazy when the 
> time is changed around.
>  
> I'm only starting to investigate this now, so I don't have all the 
> facts yet.
>  
> Can someone explain to me what reliance Wrapper has to time and how it 
> uses it... that would help me track this problem down...
>  
> Thanks a billion.... and merry-xmas and all that ;-)
>  
> Regards,
>  
> Grant