I am currently moving my scheduled tasks from an old Windows 2003 server to a Windows 7 box, both 64-bit.
As part of the migration, I am replacing a routine which created a long XML file and then started the Scheduler with one where a series of XML files are dropped into the watch folder. This has been successful, but I have discovered that sometimes the Service appears to time out, while the application does not, when an Oracle query takes a long time to return data. Is there a way of adjusting the time out of the service?
In addition there seems to a be a problem reading Excel files - I am about to try using the omniscope reader to fix this.
To set the timeout, you can customise the "wrapper.ping.timeout" property into the "wrapper.conf" file.
The default setting is 30 seconds, so if you want to increase the timeout (for example to 2 minutes) , then add the following line:
wrapper.ping.timeout=120
Also I noticed from your log that some hangs are caused by an out of memory issue. Please see here in the "Setting the memory for the Scheduler / Windows service" section how to set the service allocation memory.
I had set the memory to 10000, but the VM that it was running on only had 4096 Mb. I got that increased to the same as the prevoious one and will try again.