#129 3.2.1 outputs 'JVM exited unexpectedly' on normal stop

[Gareth Davis]

On windows (XP sp2) using the 3.2.1 of the wrapper I
get the following log entries on stopping the service:

INFO | jvm 1 | 2006/07/14 13:20:48 | INFO [Robot-
1] [Robot] - Robot is finishing
INFO | jvm 1 | 2006/07/14 13:20:48 | stop()
returning - 0
WARN | wrapper | 2006/07/14 13:20:48 | JVM exited
unexpectedly while stopping the application.
STATUS | wrapper | 2006/07/14 13:20:48 | <-- Wrapper
Stopped
STATUS | wrapper | 2006/07/14 13:20:49 | Etk queue
processing robot stopped.

The first item is the last line of code in my stop(int)
method:

public int stop(int returnCode) {
// This method should return in a timely
manner, but the robot
// may take a little while to stop, so a call
to the WrapperManager
// buys a little more time.
WrapperManager.signalStopping(30 * 1000); //
takes milliseconds

this.robot.stop();

System.out.println("stop() returning - "+
returnCode);
return returnCode;
}

If I swap to version 3.2.0 of wrapper.dll, wrapper.jar
and wrapper.exe I get the following:

INFO | jvm 1 | 2006/07/14 13:18:25 | INFO [Robot-
1] [Robot] - Robot is finishing
INFO | jvm 1 | 2006/07/14 13:18:25 | stop()
returning - 0
STATUS | wrapper | 2006/07/14 13:18:26 | <-- Wrapper
Stopped
STATUS | wrapper | 2006/07/14 13:18:27 | Etk queue
processing robot stopped.

The line 'JVM exited unexpectedly while stopping the
application' is not present.

[Leif Mortenson]

Logged In: YES
user_id=228081

Gareth,
Could you please set wrapper.debug=true in your
configuration file and rerun your test with 3.2.1. I would
like to see what the wrapper thinks is happening.

Please attach the log file with the upload button rather
than posting it inline. The line wrapping is painful. :-)

Cheers,
Leif