Automic Workload Automation

  • Private Community
Back to discussions
Expand all | Collapse all

Why does a job gets stuck in "Generating" state? and What does it mean?

  • 1.  Why does a job gets stuck in "Generating" state? and What does it mean?

    Posted May 23, 2019 02:29 AM

    Hello All,

     

    Certain jobs are getting stuck in "Generating" state, due to which the successor job isn't running. The job which is in "generating" state has in fact completed normally. However, the job is not getting marked as "Ended_Ok Ended normally" state, this is impacting the successor job's execution.

     

    Please advise.

     

    Thanks!



  • 2.  Re: Why does a job gets stuck in "Generating" state? and What does it mean?

    Posted May 23, 2019 02:57 PM

    Hi,

     

    maybe you run into this latest bug

     

    AWA 12.1 Jobhänger und falscher Job-Status 

     

    We can have just a suspicion and it seems this is related to a bug which is fixed in following AE versions:

    Automation Engine 12.2.1 - planned release date: 2018-10-31

    Automation Engine 12.3.0 - planned release date: 2019-06-28

    Automation Engine 12.2.2 - planned release date: 2019-02-27

    It's a synchronization problem between CCM and MAIN thread in job messenger, actually it doesn't have any effect on agent core.

    1. Messenger MAIN thread initiate connection to agent.

    2. After handshake, MAIN waits for EXDATA message in ccm_receive_message() function. Due to agent replies EXDATA very fast, MAIN can grab this message without going idle, meaning 1 wakeup signal remains in wake-up queue.

    3. MAIN thread sends MELD message to agent and waits for QUITT again in ccm_receive_message() function.

    4. Because there is still a wakeup signal in CCM, ccm_receive_message() returns immediately with empty queue result and messenger shuts down before it could send MELD message.

     

    Thx & rgds

    Christian