6.1.4 OBSCF EOD is stuck on a job and still persist post retrying the job

This topic provides the systematic instructions to resolve the scenario where OBSCF EOD specific job is stuck in In-progress/Failed state.

  1. Review and Store the logs as mentioned in topic 6.3 Logs to review for EOD jobs.
  2. If there are no errors in the logs and the job remains stuck after retrying, then move on to the next step.
    1. Review and Save the logs of plato-batch-server.log and conductor-server.log (If not available then Condutor Managed Server log).
    2. If the job that is stuck is an Outstanding Transaction, then capture the thread dump of the OBSCF Finance Managed Server. For any other stuck job, a thread dump is not necessary.
      <JDKlocation>\bin\./jstack -l Process_Id_Finance_Managed_Server > threaddump.txt
          
    3. Delete the Workflow ID from the WORKFLOW table, next delete the entry from CM_TM_BRANCHEOD_INSTANCES for the specific branch and the system date.
    4. Next, retrigger the EOD from the UI for the specific branch and system date.