Re: [Wrapper-user] boot process of windows prevents wrapper-service startup

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

Mattias,
    There were a couple timing problems in 3.1.0 and 3.1.1 which have 
been fixed in 3.1.2.
Please upgrade to that version and give it a try.  I am pretty sure that 
this problem has
been fixed.  Read over the change log.

Mattias Ternert wrote:

> After a reboot of a  windows 2003 server our application implemented 
> as a serice with the service wrapper failed to start. Looking to the 
> wrapper log below there are somethings that puzzels me.
>
> 1. First of all the time sequenze, how can an event 13:36:44 be logged 
> after events 14:36:43 (Maybe a bug or could it be that the server on 
> boot contacts another server for sync of time?)
>
Yes the system time does appear to be getting adjusted... Not sure what 
would be
causing such a large jump.

> 2. The amount of seconds waiting for CPU time suggest that somehting 
> with the system time is wrong (1)
>
I think that may be the bug I mentioned above.

> My conclusion is that something during the boot process of the server 
> prevents CPU time to the wrapper and jvm. How to circumvent this?
>
> Is it a good idea to set wrapper.use_system_time=false to avoid 
> problems like mentioned above?
> Would setting  wrapper.startup.delay.service=30 cause the wrapper 
> waiting 30 seconds after startup of server before launching? Thus 
> maybe avoid the conflict during boot on CPU time?
>
In 3.1.2, try setting wrapper.use_system_time=false.  This should make 
the wrapper
work correctly even without setting any timeouts or using the startup 
delay.  The
delay is also working off the timer.  So if you are using system time 
then that would
still fail.

The tick timer has proved to be quite reliable.  It will be the default 
for 3.2.0 and
future versions.

Post back with results.

Cheers,
Leif

> Any other good suggestions wold be nice...
> //Mattias
>
> INFO   | wrapper  | 2004/12/14 13:34:00 | User logged out.  Ignored.
> STATUS | wrapper  | 2004/12/14 13:34:12 | Machine is shutting down.
> STATUS | wrapper  | 2004/12/14 13:34:14 | <-- Wrapper Stopped   
>                 //reboot
> STATUS | wrapper  | 2004/12/14 14:36:37 | --> Wrapper Started as Service
> STATUS | wrapper  | 2004/12/14 14:36:37 | Launching a JVM...
> INFO   | jvm 1    | 2004/12/14 14:36:43 | Wrapper (Version 3.1.0) 
> http://wrapper.tanukisoftware.org
> INFO   | jvm 1    | 2004/12/14 14:36:43 |
> INFO   | jvm 1    | 2004/12/14 14:36:44 | Application Alarm Manager 
> running.
> INFO   | jvm 1    | 2004/12/14 14:36:44 | Started:Tue Dec 14 14:36:44 
> CET 2004
> INFO   | jvm 1    | 2004/12/14 13:37:52 | JVM Process has not received 
> any CPU time for 429493180 seconds.  Extending timeouts.
>
> INFO   | jvm 1    | 2004/12/14 13:38:51 | Wrapper Manager: The Wrapper 
> code did not ping the JVM for 59 seconds.  Quit and let the Wrapper 
> resynch.
>
> STATUS | wrapper  | 2004/12/14 13:38:52 | <-- Wrapper Stopped
>
>
>