Re: [Wrapper-user] Wrapper and Time

[Grant \(ProtectionNET\) <gr...@pr...>]

Lief,

Changing the time and timezone is part of the system configuration that this
java app performs. Normally this would only occur at initial setup and
possibly only rarely so I'm going to avoid the whole issue by making the app
restart. I'm obviously still caught in a situation where wrapper still
thinks time has gone silly...

It seems as though setting the time backwards (ie changing it from 2:00pm to
10:00) causes Wrapper to report silly things like "process has not recieved
CPU time for 14308 seconds, extending timeouts" which worry me because what
is it doing when it see's this. I have also had the wrapper complain and
restart - not good.

I've not looked through the source of wrapper (perhaps I should) but why
could you not just increment an int for X times and sleep for 1 sec each
time. When you get to X you would know that the code has reached that
timeout - this makes your counters work regardless of what the real time is
outside.

I'm going to look through the source and see if I can make what I need to
work. If I figure anything out, I'll let you know.

Grant

----- Original Message ----- 
From: "Leif Mortenson" <le...@ta...>
To: <wra...@li...>
Sent: Friday, December 26, 2003 10:33 AM
Subject: Re: [Wrapper-user] Wrapper and Time


> 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
>
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
> Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user