Remove System.exit to avoid strange behavour.

[nigelsim]

When a service ends using System.exit(), such as in the MainService class, the services control reports Error 1053: The service did not respond to the start or control request in a timely fashion. If I replace this with just returning from main then everything works file.

This is an issue for me because I'd like to just use my normal main entry point, as I utilise Runtime shutdown handlers to cleanup (which also run correctly, despite the service handler freaking out).

Perhaps the answer is actually to change the way MainService runs so that it doesn't call System.exit(). This pull request runs the service in a thread, and uses the main thread to monitor.

[poidasmith]

Unfortunately some other users rely on this behaviour as they are using third party libraries that don't shut down non-daemon threads. I can certainly make it configurable via an INI option.

[nigelsim]

Fair enough. It may just be easier to provide it as a separate class given the difference is non-trivial. Just a thought.

Thanks for the project too, much appreciated.

[melloware]

Thank you for posting this. I had to use this code with 1 minor tweak to get my "Error 109: Pipe Ended" error from Windows. I added a System.exit(0) right before the return 0 to make my Spring application stop gracefully. Woks like a charm now and my service stops and starts gracefully.

      System.exit(0);
      return 0;