Unexpected service shutdown with SJSAS 9 and Windows
If SJSAS 9 is installed on Windows as a service and a user logs into the console and log out again, SJSAS goes down hard.It appears that Windows sends the equivalent of a SIGKILL to processes the user doesn't own , or something equally wierd.
Either way, adding the -Xrs JVM option to the domain.xml for the domain fixes the issue.
Would it be reasonable to ask that in a future release this be done by default for Windows installs if the user checks "Install as a service"?

