Automic Workload Automation

Expand all | Collapse all

Jobs do not start because of max resource usage limit even if no job is running

  • 1.  Jobs do not start because of max resource usage limit even if no job is running

    Posted 11-08-2018 06:06 AM

    Hi,

    I have a agent with  WORKLOAD_MAX_JOB=32.

    Everything works until, almost daily, nothing else gets executed because the max resource usage limit is hit even though no jobs are running on the agent.

    Looks like something is holding the resources but I have no clue what.

    The issue is solved with a restart of the agent.

     

    Is there anything I can check? Can this be a bug?

     

    Best,

    Marco



  • 2.  Re: Jobs do not start because of max resource usage limit even if no job is running

    Posted 11-09-2018 08:40 AM

    Does the Agent log show anything?

     

    Which Agent version?

     

    Isit reproducible?

     

    cheers, Wolfgang



  • 3.  Re: Jobs do not start because of max resource usage limit even if no job is running

    Posted 11-09-2018 09:39 AM

    The agent prints nothing in logs.

    Agent version is 12.2.0 build.1034

    It's not deterministic, it happens every two/three days and only in our test environments but on all agents allocated for these jobs.

     

    Best,

    Marco