Batch Status Stucked In Started Status Even When There Is An Error On The Batch Run (Doc ID 2905283.1)

Last updated on MAY 29, 2024

Applies to:

Symptoms

On : 2.8.0.0.0 version, Framework

Batch Status stuck in Started status even when there is an error on the batch run

Having issues with batch running on our C2M 2.8 development environment.

1. When submitting a batch and it errors out, the Batch Job Submission record remains in Started status, even though it has already errored out. When trying to create a new job submission, the batch job just stays in pending status. Customer need to restart the threadpool worker in order for it to pick up the new jobs. This is affecting our productivity as we have to restart the threadpoolworker over and over.

2. Recent Changes:
a. Customer noticed this issue this week when after our app server migration, though some developers say that it was already happening last week after our database migration, still not sure if this happened because of the server migrations or because of an applied patch.
b. Applied the March 2022 rollup patch a few weeks ago (Aug 13).
c. Most recent patches applied are 34000442 and 33998461 last Aug 28.
d. Not experiencing the issue in our staging environment which was also migrated but has not been patched yet with the march 2022 roll-up.

4. When the customer tried running it on our STG environment which does not have the March Patch Rollups yet, the batch behaves correctly as expected.

ERROR
-----------------------
- 2022-08-30 08:01:42,711 [SchedulerDaemon] INFO (support.cluster.ClusterBasedThreadPoolChecker) Not offerring thread to job BatchJobQueue_Id(18072011193063) since a previous submission is already running
 - 2022-08-30 08:01:52,762 [SchedulerDaemon] INFO (support.cluster.ClusterBasedThreadPoolChecker) Not offerring thread to job BatchJobQueue_Id(18072011193063) since a previous submission is already running
 - 2022-08-30 08:02:02,817 [SchedulerDaemon] INFO (support.cluster.ClusterBasedThreadPoolChecker) Not offerring thread to job BatchJobQueue_Id(18072011193063) since a previous submission is already running
 - 2022-08-30 08:02:12,818 [SchedulerDaemon] INFO (support.cluster.AbstractDaemon) Executing SchedulerDaemon iteration 90, threadIsAlive=true, isInterrupted=false
 - 2022-08-30 08:02:12,871 [SchedulerDaemon] INFO (support.cluster.ClusterBasedThreadPoolChecker) Not offerring thread to job BatchJobQueue_Id(18072011193063) since a previous submission is already running
 - 2022-08-30 08:02:12,872 [SchedulerDaemon] INFO (support.cluster.AbstractDaemon) Finished SchedulerDaemon iteration 90, taking 53 ms, will sleep 10 seconds before next iteration
 - 2022-08-30 08:02:22,925 [SchedulerDaemon] INFO (support.cluster.ClusterBasedThreadPoolChecker) Not offerring thread to job BatchJobQueue_Id(18072011193063) since a previous submission is already running
 - 2022-08-30 08:02:32,982 [SchedulerDaemon] INFO (support.cluster.ClusterBasedThreadPoolChecker) Not offerring thread to job BatchJobQueue_Id(18072011193063) since a previous submission is already running
 - 2022-08-30 08:02:43,038 [SchedulerDaemon] INFO (support.cluster.ClusterBasedThreadPoolChecker) Not offerring thread to job BatchJobQueue_Id(18072011193063) since a previous submission is already running
 - 2022-08-30 08:02:53,110 [SchedulerDaemon] INFO (support.cluster.ClusterBasedThreadPoolChecker) Not offerring thread to job BatchJobQueue_Id(18072011193063) since a previous submission is already running
 - 2022-08-30 08:03:03,138 [pool-4-thread-1] INFO (support.cluster.CancelBatchJob) Found job=BatchJobQueue_Id(18072011193063) with batch code=CMDEPAPP in Pending cancel status

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
Dev Environment
Replication
SAMPLE SCENARIO 1: VALIDATE IF THE FACT - BO NAME BATCH PARAMETER
IS A VALID BUSINESS OBJECT
Setup
1. BATCH JOB SUBMISSION
2. Run CMPYTOFT Batch
3. CM-DistributePaymentToFZZ is an invalid Business Object
Result
4. BATCH RUN SUBMISSION
5. Batch Job Status is stuck in Started status.
6. Error is raised in Batch Run Tree.

SAMPLE SCENARIO 2: VALIDATE BATCH PARAMETER
Setup
1. BATCH JOB SUBMISSION
2. Run CMHCSCUS Batch
3. Valid Start Date is YYYY-MM-DD
Result
4. BATCH RUN SUBMISSION
5. Batch Job Status is stuck in Started status.
6. Error is raised in Batch Run Tree.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.