8 Replies Latest reply on Jun 14, 2018 8:12 AM by Imre Csoka

    "JOB FAILED TO EXECUTE DUE TO FORK FAILURE"

      I have a job that processes hundreds of thousands of files. After about 3 hours to 3 and a half hours the log for Control-M states "JOB FAILED TO EXECUTE DUE TO FORK FAILURE" and it marks the job as "NOT OK" in Control-M. The job itself is still processing in the application so the job is indeed NOT dead but Control-M is thinking it is. Is there a convenient way to change the timeout for the job or for the agent to say 10 hours so this will not happen? The return code is -1 which is typically a communications failure so it seems as if something is happening and it stops communicating with the agent?