[Wrapper-user] Wrapper 2.2.9.1 causing System.exit(1)

[Nazim N. <na...@ho...>]

Hi,

I am running RMI server using wrapper 2.2.9.1 as service on Windows 2000 =
Server. It uses log4j for logging. When I set root priority level to =
debug in log4j config file (not wrapper config file), it terminates =
abnormally while starting up. Works fine if I set the priority level to =
info. I get the following in wrapper log after wrapper gives up:

INFO   | jvm 8    | 2003/03/02 15:44:57 | calling System.exit(1)
INFO   | jvm 8    | 2003/03/02 15:44:57 | 28470 [Thread-2] DEBUG =
com.workforcesoftware.Policy.AllPolicies  - Loading Formula: _796BA2E4
DEBUG  | wrapperp | 2003/03/02 15:44:57 | read a packet 107 : 0
DEBUG  | wrapper  | 2003/03/02 15:44:57 | JVM signalled that it was =
stopped.
DEBUG  | wrapperp | 2003/03/02 15:44:57 | socket read no code (closed?).
INFO   | wrapper  | 2003/03/02 15:44:57 | Wrapper Process has not =
received any CPU time for 29 seconds.  Extending timeouts.
DEBUG  | wrapper  | 2003/03/02 15:44:57 | JVM Ping Failed.
ERROR  | wrapper  | 2003/03/02 15:44:57 | JVM exited unexpectedly.
DEBUG  | wrapper  | 2003/03/02 15:44:57 | JVM was only running for 97 =
seconds leading to a failed restart count of 5.
FATAL  | wrapper  | 2003/03/02 15:44:57 | There were 5 failed launches =
in a row, each lasting less than 300 seconds.  Giving up.
FATAL  | wrapper  | 2003/03/02 15:44:57 |   There may be a configuration =
problem: please check the logs.
STATUS | wrapper  | 2003/03/02 15:44:58 | <-- Wrapper Stopped

After the failure of each launch i just see:

INFO   | jvm <n>    | <date> | calling System.exit(1)

Don't see any useful message. Also it is a quad processor machine.

The surprising thing is that it works fine with the same configuration =
(i.e log4j priority level set to debug) on a single processor machine =
that has Windows 2000 server.

Is there something related to above fixed in 3.0.0?

Thanks
-Nazim