"Process is already running" error with reference to an execution ID which has completed

Document created by john_yocum067395 Employee on Apr 14, 2017Last modified by frank_wetzler970218 on Dec 19, 2017
Version 4Show Document
  • View in full screen mode

You may run into a scenario where a process execution returns the error "Process is already running {executionId}" but when you view that executionId, the process has completed successfully.



In the container logs of the molecule running into this issue there will be a message similar to:

Mar 23, 2017 10:45:42 AM EDT WARNING [com.boomi.container.cloudlet.execution.ClusterExecutionTaskTracker getCurrentExecutionId] Found orphaned(?) process 82b741a7-83dc-42ca-8868-e55adafbda6e lock (exec execution-f1e60ca6-89e3-4f9b-8e15-6668d375bb73-2017.03.23 seemingly held by 192_168_0_200)

Mar 29, 2017 10:45:42 AM EDT WARNING [com.boomi.container.cloudlet.execution.ClusterExecutionTaskTracker getCurrentExecutionId] Could not acquire lock for ExecutionSubmission: ExecutionTaskConfig



A process lock can become orphaned if the node that executed the process becomes unstable and/or loses communication between the other nodes in the cluster. The process lock file, displayed as {executionId}.lck, is found under the '<atom_install>/execution/current' folder in the atom installation directory.



Once the erroneous node becomes stable again you will see the molecule release the orphaned lock file to allow future executions to kick off:

Mar 23, 2017 4:10:19 PM EDT INFO [com.boomi.container.cloudlet.execution.ClusterExecutionTaskTracker cleanupExecutionTracking] Attempting to acquire process lock on suspected orphaned lock file {location of lock file}

Mar 23, 2017 4:10:19 PM EDT WARNING [com.boomi.container.cloudlet.execution.ClusterExecutionTaskTracker cleanupExecutionTracking] Releasing orphaned process e1a0d30f-eb96-4457-9199-58c970c36817 lock (exec execution-9e0ccb9a-5f9b-4f32-b0cf-5ff5ca2fc648-2017.03.23)

1 person found this helpful