Best way to stop long running workflow | Community
Skip to main content
Peter_Puzanovs
Peter_Puzanovs
New Participant
January 12, 2016
Solved

Best way to stop long running workflow

  • January 12, 2016
  • 6 replies
  • 6591 views

Hi,

 

Best practice question here, have a workflow that has been running for couple of days now on a single file that is normally processed in seconds...

 

What is the best way to stop this file processing job.

 

Without damaging anything on the Author instance ideally?

 

 

Thanks,

Peter

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by Peter_Puzanovs

    Hi Jorg,

    Unfortunately, simple restart did not stop background process...

    Following steps seem to stop the background process:

     

    1. Make sure workflows are terminated via the normal /workflows window.

     

    1. Open ip:port/system/console/bundles:

     

    STOP Adobe - XMPFiles Worker host com.adobe.xmp.worker.files.host                            

    STOP Adobe XMPCore com.adobe.xmp.xmpcore5.0.20

    STOP Day Communique 5 DAM Asset Handler Implementationcom.day.cq.dam.cq-dam-handler 5.6.6                           

    STOP Day Communique 5 WCM Workflow com.day.cq.wcm.cq-wcm-workflow 5.6.4                  

    STOP Day Communique 5 Workflow Implementation com.day.cq.workflow.cq-workflow-impl 5.6.8

     

    RESTART CQ BOX

     

    START Adobe - XMPFiles Worker host com.adobe.xmp.worker.files.host                          

    START Adobe XMPCore com.adobe.xmp.xmpcore5.0.20

    START Day Communique 5 DAM Asset Handler Implementationcom.day.cq.dam.cq-dam-handler 5.6.6                           

    START Day Communique 5 WCM Workflow com.day.cq.wcm.cq-wcm-workflow 5.6.4                

    START Day Communique 5 Workflow Implementation com.day.cq.workflow.cq-workflow-impl 5.6.8

     

    RESTART CQ BOX

     

    Thanks,

    Peter

    6 replies

    S
    SHKHAN-1
    Employee
    May 2, 2018

    Very helpful

    Peter_Puzanovs
    Peter_PuzanovsAuthorAccepted solution
    New Participant
    January 15, 2016

    Hi Jorg,

    Unfortunately, simple restart did not stop background process...

    Following steps seem to stop the background process:

     

    1. Make sure workflows are terminated via the normal /workflows window.

     

    1. Open ip:port/system/console/bundles:

     

    STOP Adobe - XMPFiles Worker host com.adobe.xmp.worker.files.host                            

    STOP Adobe XMPCore com.adobe.xmp.xmpcore5.0.20

    STOP Day Communique 5 DAM Asset Handler Implementationcom.day.cq.dam.cq-dam-handler 5.6.6                           

    STOP Day Communique 5 WCM Workflow com.day.cq.wcm.cq-wcm-workflow 5.6.4                  

    STOP Day Communique 5 Workflow Implementation com.day.cq.workflow.cq-workflow-impl 5.6.8

     

    RESTART CQ BOX

     

    START Adobe - XMPFiles Worker host com.adobe.xmp.worker.files.host                          

    START Adobe XMPCore com.adobe.xmp.xmpcore5.0.20

    START Day Communique 5 DAM Asset Handler Implementationcom.day.cq.dam.cq-dam-handler 5.6.6                           

    START Day Communique 5 WCM Workflow com.day.cq.wcm.cq-wcm-workflow 5.6.4                

    START Day Communique 5 Workflow Implementation com.day.cq.workflow.cq-workflow-impl 5.6.8

     

    RESTART CQ BOX

     

    Thanks,

    Peter

      joerghoh
      joerghoh
      Employee
      January 14, 2016

      Hi Peter,

      when the workflow is visible in the threaddumps, it is obviously still running. But then you also determine where it has stalled. Based on the outcome of this check a simple restart could help.

      Jörg

      G
      Gunars_V
      New Participant
      January 13, 2016

      You can try terminating the workflow under the workflow console: /libs/cq/workflow/content/console.html

      Click on the "Instances" tab, select the workflow, right-click and terminate.

        Peter_Puzanovs
        Peter_PuzanovsAuthor
        New Participant
        January 12, 2016

        Hi,

        Thank you for your reply,

        Yep, it's running as it's been clearly visible in the thread dumps. Also in the dam assets I can see icon that indicates workflow is still running. Logs indicate same.

        Thanks,

        Peter

        P
        PaulMcMahon
        New Participant
        January 12, 2016

        Are you actually sure that the process is still running? It's possible that the process either never launched or ended abnormally but left the workflow in a stalled state. Have you checked the logs around the time the workflow kicked off for error messages that might indicate a problem in the process?

        Are you seeing log output that indicates the job is still running? Or looked at thread dump and seen the thread running? Short of a restart I am not sure there is any way to ensure that the thread. You can try moving the workflow back a step, or terminating it and restarting, but there is no guarantee that thread from the previous job has stoppped. 

        Terms & ConditionsAccessibility statement

        Loading footer...