Not on all our Windows machines, but on some of them, when the
wrapper is started as a service and then the user logs off from
their console session, the Java
process that the wrapper is managing is stopped (with shutdown hook
execution). Then the wrapper notices that the Java process has stopped
and restarts it.
I have argued that it must be some funky Windows setting that does it
but, being the wrapper advocate here, I have been stuck with figuring
out why.
Any help is welcome (and no I can not convince everyone to switch to
Linux).
Richard
--
This email message is for the sole use of the intended recipient(s) and
may contain confidential information. Any unauthorized review, use,
disclosure or distribution is prohibited. If you are not the intended
recipient, please contact the sender by reply email and destroy all
copies of the original message.
|
