All Threads in a Thread Pool Seem to be "stuck" and Need the Batch Queues Cleared
(Doc ID 2043024.1)
Last updated on AUGUST 12, 2020
Applies to:Oracle Financial Services Revenue Management and Billing - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
ORMB batch job fails to complete then all threads on one or more thread pools either remains in Pending or do get started but do not complete any work.
The java process (VM) of a thread pool, which do not start or complete any work, can be identified by the high CPU usage.
Looks like a busy wait in the thread pool.
The thread pools can end up in a state where it cannot run any threads successfully when:
1) The thread pools where started with too short a time interval, for example, less than ~30 seconds
2) After the successful completion of one of the custom batch jobs
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