#69 LOGOFF_EVENT (202) causes service app not to run savely

[m.hilpert]

Today, my service didn't process any requests anymore.
in My log file, the last entry was:

Service Wrapper control event: 202

Even though I don't handle this specifically:

-------------------
/**
* Implements WrapperListener.
* Called whenever the native wrapper code traps a
system control signal against the Java process.
* It is up to the callback to take any actions
necessary. Possible values are:
WrapperManager.WRAPPER_CTRL_C_EVENT,
* WRAPPER_CTRL_CLOSE_EVENT,
WRAPPER_CTRL_LOGOFF_EVENT or
WRAPPER_CTRL_SHUTDOWN_EVENT.
*
* @param event The system control signal.
*/
public void controlEvent(int event) {
logger.info("Service Wrapper control
event: "+event);

if (!WrapperManager.isControlledByNativeWrapper
()) { //not handled by wrapper?
if ((event ==
WrapperManager.WRAPPER_CTRL_C_EVENT) || //200
(event ==
WrapperManager.WRAPPER_CTRL_CLOSE_EVENT)
|| //201
(event ==
WrapperManager.WRAPPER_CTRL_SHUTDOWN_EVENT))
{ //203
WrapperManager.stop(0); //trigger a
shutdown of the JVM
}
}//else: handled by wrapper
}//controlEvent()
--------------------------------

So, as i don't catch the 202 event, the wrapper should
also don't do anything specific. Or is there any internal
change?

[Leif Mortenson]

Logged In: YES
user_id=228081

I just went back and retested this and it appears to be
working fine for me.

Is this something that you are able to reproduce? If so, I
would like you to set the wrapper.debug=true property in
your wrapper.conf file and then attach the resulting
wrapper.log file.

What happened in the wrapper.log file after you logged out?
You should have seen a message as follows:
INFO | wrapper | 2004/11/12 18:00:28 | User logged out.
Ignored.

If the JVM hung for any reason then the Wrapper should have
restarted it? This extra information will help me to give
you a useful answer.

Cheers,
Leif

[m.hilpert]

Logged In: YES
user_id=667728

Unfortunatley, this ServiceWrapper error code (202) didn't
happen again, so far. The wrapper didn't restart the JVM -
the application just stopped running.