AutoSys Workload Automation

 View Only
Expand all | Collapse all

Tuesday Tip: CA WA SAP Agent job stuck in running or ready state

  • 1.  Tuesday Tip: CA WA SAP Agent job stuck in running or ready state

    Broadcom Employee
    Posted May 28, 2013 04:44 PM
    Users may sometimes notice that their SAP jobs get stuck in 'RUNNING' or 'READY' status. The jobs do not complete and require manual intervention. The problem is most likely caused by the fact that many jobs get submitted at once and the agent had a problem with submitting them all at the same time. It depends on the speed of the connection to SAP and performance of the SAP system.
    This problem can be resolved by adding a delay between job submissions. Add the following parameter to the agentparm.txt.

    [color=#2100fc]sap.job.handler.sleep.interval=1000ms[color]
    Default value is 300 ms (milliseconds).
    Increase the value to 1000 ms to give a bit of a gap between job submissions. Once the agentparm.txt has been edited, restart the agent.
    [color=#2100fc]Note[color]: The parameter can be added any where in the, but it is good idea to add it by SAP plugin properties.


  • 2.  RE: Tuesday Tip: CA WA SAP Agent job stuck in running or ready state

     
    Posted May 30, 2013 02:49 PM
    Thanks for the tips!


  • 3.  RE: Tuesday Tip: CA WA SAP Agent job stuck in running or ready state

    Broadcom Employee
    Posted May 30, 2013 08:39 PM
    Another option ( depending on the scheduler being used) would be to set up a virtual machine with two agent - so that the workload could be distributed over the two machines