Hey there --
Recent events have shown me there may be use for killing a 'rogue' job that for some reason is taking an hour+ (most of my jobs take anywhere from seconds to maybe 6-7 minutes tops).
IE -- recently I noticed the remote server running my job was having hardware issues. Temporarily, I will probably have a backup machine run the incremental jobs as well.
However I need a way to kill a hour+ job if such an event happens again.
Simplest way I can think of right now is to say ... if I start all the jobs at midnight typically ... just have a .bat file with /kill javaw.exe start at 1 or 2 am.
This would suffice but I wonder if there is a more sensible way, like a command line message to simply stop the job.
Recent events have shown me there may be use for killing a 'rogue' job that for some reason is taking an hour+ (most of my jobs take anywhere from seconds to maybe 6-7 minutes tops).
IE -- recently I noticed the remote server running my job was having hardware issues. Temporarily, I will probably have a backup machine run the incremental jobs as well.
However I need a way to kill a hour+ job if such an event happens again.
Simplest way I can think of right now is to say ... if I start all the jobs at midnight typically ... just have a .bat file with /kill javaw.exe start at 1 or 2 am.
This would suffice but I wonder if there is a more sensible way, like a command line message to simply stop the job.