We happened to have installed Hudson (3.1.0) on a VM with Windows 7 Pro (ESXI). Hudson also has been configured as a service. Regarding the scheduling of cron jobs, Hudson always fails to start at the desired cron time. Although if someone connects with the browser (remote or local), it starts a job and defines the trigger als timely controlled. We've changed the trigger time to everything possible and checked the results for more than 3 weeks until now:
From my point of view, it seems jetty might get in a standby mode and reactivates itself on client connect (browser), although the thread (java) has -Xrs parameter to prevent shutting Hudson down on logoff. Has anyone experienced the same behavior or any clue what else I can look for? Maybe it's also my VM going to standby mode, which I can't think of, but I'll check again.
None of my examples are working, execpt when I remotely open hudson through the browser. Hudson even tries to run a job on the mentioned event (open browser), although it may not be the scheduled time at that moment.
I'm starting hudson with the executable file (*.exe), and installed a service (start type: automatic) as well. It seems that the compabillity feature from Windows is also affecting this behavior and I don't think setting this executable to run als "Administrator" will do the trick.
I will try your solution (create batch file and run hudson.war with java) and also install the batch file as a service. Maybe that will help...
It may be that the executable is only for testing purpose, specially on windows having those user security feature may influence hudsons behavior. I'll also keep the community updated with my experience.
Sorry for the absence, I just had other tasks prioritized in the meantime.