Kill a "currently running" job
Posted: 03 Mar 2015 6:46
If I have a job that runs every 5 minutes pending the completely of a previous run, is there a way to put a time limit on the job? We've had situations where a client server application has had an outage, but the CM job running against that application at the time of the outage shows "currently running" in the sysout, and will remain that way until it's manually killed. That creates a business problem since these need to run every 5 minutes.
Any way to get around this?
Any way to get around this?