|
From: john y. <joh...@fa...> - 2004-03-09 16:08:23
|
Hi, All, We have been using the wrapper for some win NT services. Recently we occasionally ran into some problem where the services consume almost all (99%, 100%) the CPU resources of a dual-CPU machine. The following is a segment of the wrapper log file: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D INFO | jvm 1 | 2004/02/18 06:31:25 | Send a packet 103 : ok DEBUG | wrapperp | 2004/02/18 06:31:25 | read a packet 103 : ok DEBUG | wrapper | 2004/02/18 06:31:25 | Got ping response from JVM DEBUG | wrapper | 2004/02/18 06:31:26 | ServiceControlHandler(4) DEBUG | wrapper | 2004/02/18 06:31:26 | SERVICE_CONTROL_INTERROGATE DEBUG | wrapperp | 2004/02/18 06:31:31 | sent 6 bytes INFO | jvm 1 | 2004/02/18 06:31:31 | Received a packet 103 : ping INFO | jvm 1 | 2004/02/18 06:31:31 | Send a packet 103 : ok DEBUG | wrapperp | 2004/02/18 06:31:31 | read a packet 103 : ok DEBUG | wrapper | 2004/02/18 06:31:31 | Got ping response from JVM DEBUG | wrapperp | 2004/02/18 06:31:37 | sent 6 bytes DEBUG | wrapper | 2004/02/18 06:31:37 | ServiceControlHandler(4) Dvm 1 | 20E0UG4/02 | 18 06wrapper | 31:37 | Received a packet 103 : ping Dvm 1 | 20E0UG4/02 | 18 06wrapper | 31:37 | Received a packet 103 : ping 2004/02/18 06:31:37 | SERVICE_CONTROL_INTERROGATE STATUS | wrapper | 2004/02/18 10:38:00 | --> Wrapper Started as Service DEBUG | wrapperp | 2004/02/18 10:38:00 | server listening on port 17005. DEBUG | wrapper | 2004/02/18 10:38:00 | JVM was only running for -322562155 seconds leading to a failed restart count of 1. STATUS | wrapper | 2004/02/18 10:38:00 | Launching a JVM... =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D From which we can see that at 6:31:37 something went wrong. There are two lines in the log are exactly the same and the contents are sort of mixed. It should be something like: DEBUG | wrapper | 2004/02/18 | 06:31:37 | Received a packet 103 : ping Instead, it came out mixed as: Dvm 1 | 20E0UG4/02 | 18 06wrapper | 31:37 | Received a packet 103 : ping Dvm 1 | 20E0UG4/02 | 18 06wrapper | 31:37 | Received a packet 103 : ping The DEBUG and the date time were mixed. There was a 'B' in the 'DEBUG' missing. the 'J' for 'Jvm 1' was also missing. During that time, the service shown active in the windows service manager panel. But the actual service was hung.=20 It seems that there was something happening inside the wrapper native part. Have anyone ever got the similar situation like this? Could anyone suggest what was happening here? Thanks, --=20 http://www.fastmail.fm - And now for something completely different=85 |