|
From: Mattias T. <Mat...@mi...> - 2004-12-15 13:51:38
|
Hi 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.=20 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?) 2. The amount of seconds waiting for CPU time suggest that somehting = with the system time is wrong (1) 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=3Dfalse to avoid = problems like mentioned above? Would setting wrapper.startup.delay.service=3D30 cause the wrapper = waiting 30 seconds after startup of server before launching? Thus maybe = avoid the conflict during boot on CPU time? 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 |=20 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 |