Re: [Wrapper-user] Extending Timeouts error

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

Andre,
    Sorry for the slow reply.   The message that you posted is actually not
a problem.   It is simply saying that the Wrapper and JVM processes did
not receive any CPU for 5389 seconds.  Then notifying you that it has
extended all of its internal timeouts appropriately.
    If the JVM was actually hung then the Wrapper would have told you that
it timed out waiting for a response from the JVM and the JVM would have
been restarted.  I don't think that your JVM was having any problems at this
point.

    This can happen for a number of reasons.
1) Another process is consuming 100% of all CPU at a high priority for
a long period of time.   Some backup systems do this.

2) Your system was suspended to memory or disk for the specified time
and then restored.

3) Your system time was set forward by 5389 seconds.

    The current default timing mechanism of the Wrapper is based off of the
system time and is affected by system time changes and other applications
consuming lots of CPU.   In most cases the Wrapper recovers correctly
with no ill effects, but at times you can end up with the JVM being 
restarted.
For example setting the system time back by more than 30 seconds or so
will often result in the JVM being restarted.

    To resolve these problems, a tick based timer mechanism was added in
version 3.1.0.   It is still considered experimental until it has had a 
chance to
get more live testing.   The 3.1.0 release had a few related bugs on 
multi cpu
systems.  But they have been fixed in the 3.1.1 release.  If no further
problems are discovered in that release then I will most likely make it the
default timer for the 3.1.2 or 3.1.3 release.

Cheers,
Leif


Andre Harry wrote:

>Hi,
>
>Im using version 3.0.2
>
>and it's been running okay for a while but recently
>we're having problems, it keeps crashing and sometimes
>just hung. However, the service is not restarted as it
>is said on the website. We didnt realise it until the
>next day that it crashed.
>
>Sometimes there's no error message in the log file, it
>just exited, however today i have this error message:
>
>INFO   | wrapper  | 2004/06/02 10:18:21 | Wrapper
>Process has not received
>any CPU time for 5389 seconds.  Extending timeouts.
>INFO   | jvm 1    | 2004/06/02 10:18:21 | JVM Process
>has not received any
>CPU time for 5388 seconds.  Extending timeouts.
>
>and i dont know understand what the problem is. And
>how to make the service restarts automatically? do i
>need to set it up in the config file? or should it be
>done automatically?
>
>Thanks for the help
>Andre
>  
>