Just noticed that in 3.1.2, the Wrapper process is
correctly ignoring TERM singals, but if a TERM signal
is sent to the JVM process it will cause the JVM to
shutdown. Because this is considered a normal
shutdown, the Wrapper will also stop.
The JVM should be ignoring the TERM singnals in this case.
Leif
Logged In: YES
user_id=228081
Ok, this has been fixed for the 3.2.0 release.
TERM signals were being passed to the WrapperManager as
WRAPPER_CTRL_SHUTDOWN_EVENT events. These are not supposed
to be ignored on Windows. To differentiate between these
two events and thus function correctly a new
WRAPPER_CTRL_TERM_EVENT was added.
Leif