Some Java Service application have a problem with the Java process exiting whenever a
user logs out under Windows. Several people have asked about whether or not the
Wrapper handles this. The answer is that the Wrapper has handled this correctly since
its first release.
The Java side of the Wrapper requires a native library to make this work. (Wrapper.DLL
on Windows and libwrapper.so on Unix systems.) The native library is responsible for
trapping all system signals sent to the JVM process and handling them correctly.
A Java Application may handle these signals by implementing the
controlEvent method in the
WrapperListener interface.
If you are experiencing any problems with your JVM being restarted by the Wrapper when
a user logs out, please verify that the library is being loaded. If it is not, then a
warning message will be displayed in the JVM output during the WrapperManager
initialization.
You can find examples of what happens the user logs out while Wrapper is being run as
a console application and as a service in the Examples
section of the documentation.