Batches Are Failing Due To Threads In Pending/terminated State
(Doc ID 2917885.1)
Last updated on JANUARY 03, 2023
Applies to:
Oracle Utilities Customer Care and Billing - Version 2.6.0.1.0 and laterInformation in this document applies to any platform.
Goal
On : 2.6.0.1.0 version, UT - Utilities
Batches are failing due to threads in pending/terminated state
Batch failed due to “The thread execution was terminated due to a user request received from a JMX client console”, and the thread went into an error state.
In Oracle, we found <patch 29327381> to solve this issue. This patch has been already installed in our environments, but this issue is occurring frequently.
We get several failures daily due to pending threads or threads getting terminated.
ERROR:
--------
14:25:19,370 [TPW_GENERALWorker:4] ERROR (com.splwg.base.api.batch.AbstractExecutionStrategy) Thread execution aborted: BatchThreadInstance_Id(batchThreadId: [batchRunId: [batchControlId: [F1-FCTRN], batchNumber: 26485, batchRerunNumber: 0], batchThreadNumber: 4], batchInstance: 18505638)
com.splwg.base.api.batch.ThreadAbortedException: (Server Message)
Category: 11001
Number: 1304
Call Sequence:
Program Name:
Text: Canceled by user connected as pool-3-thread-3
Description: The thread execution was terminated due to a user request received from a JMX client console.
Table: null
Field: null
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| References |