Automic Workload Automation

Expand all | Collapse all

Stopped client still running jobs

  • 1.  Stopped client still running jobs

    Posted 02-01-2018 10:03 AM
    Hello,

    Just a quick question ...

    I have a client that is showing as stopped from client 0 ..

    The queue in the client is showing as started ...

    I can still run jobs in this client.

    Should this behavior happen?

    Cheers,

    Dan.


  • 2.  Stopped client still running jobs

    Posted 02-01-2018 10:25 AM
    FrankMuffke

    Not to question you, you know more about Automic than I do, but please elaborate. Do you mean this part?

    "While a client is being stopped, you can still activate tasks."

    Will they only be activated, or also run? And if they do in fact also run, then what's the point? :)



  • 3.  Stopped client still running jobs

    Posted 02-01-2018 10:09 AM
    I can still run jobs in this client.
    We saw this once, too: Minutes after stopping a client, a job was started in that client.


    Should this behavior happen?


    No.

    Sorry to say we didn't investigate it further at the time. But it's not unheard of ...

    (edit: Just a thought: Could it be that the job was already activated or activating?)


  • 4.  Stopped client still running jobs

    Posted 02-01-2018 10:30 AM
    Cheers Harald .. that explains the behavior then .. I was starting the jobs manually from the client.


  • 5.  Stopped client still running jobs

    Posted 02-02-2018 04:05 AM
    Cheers again for the time and effort to respond.

    Dan


  • 6.  Stopped client still running jobs

    Posted 02-01-2018 10:26 AM
    Hello,

    Thanks for both the responses ...

    This was a newly created client (via the API) and the queue was started also via the API.

    The client had therefore never been started or stopped.

    Just thought it was a little strange that's all.

    Cheers,

    Dan.


  • 7.  Stopped client still running jobs

    Posted 02-01-2018 10:28 AM
    If the client is stopped, no automated processes will start. E.g. a schedule object will not start its tasks, or Event will not trigger, or a periodical started task will also not start while the client is stopped.

    Manual activated tasks will still run, and also the activations which were started before the client is stopped, will still finish. If on a stopped client you start a workflow or a job, it will run.


  • 8.  Stopped client still running jobs

    Posted 02-01-2018 12:22 PM
    If your goal is to stop task submission, then close the queues.  Any newly submitted tasks will wait for a queue to open.


  • 9.  Stopped client still running jobs

    Posted 02-01-2018 12:28 PM
    Once more Pete was quicker than me with my editet posting...


  • 10.  Stopped client still running jobs

    Posted 02-01-2018 10:15 AM
    Sorry to contradict you, Carsten, bur YES this may happen.

    strange but ...... by design ...... ;-)

    Explanation here:
    https://docs.automic.com/documentation/webhelp/english/ALL/components/AE/11.2/All%20Guides/help.htm#ucaacp.htm?Highlight=mandant%20stop

    cheers, Wolfgang


  • 11.  Stopped client still running jobs

    Posted 02-01-2018 10:58 AM
    Thx, Harald was quicker than Austrian Railservice WIFI .... :-)

    Furthermore this means, if you want a client to be "really stopped" you should Stop the clients AND the queues.

    cheers, Wolfgang


  • 12.  Stopped client still running jobs

    Posted 02-01-2018 12:49 PM
    We gotta stop working the same hours.... LOL!