Robustness Problems With CC&B
(Doc ID 1386535.1)
Last updated on SEPTEMBER 15, 2022
Applies to:Oracle Utilities Framework - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
**Examples provided in this article do not represent real life personal/confidential information**
**Disclaimer:** This KM article may include the following abbreviations:
CCB - Oracle Utilities Customer Care and Billing
JVM - Java Virtual Machine
DB - Database
OUAF/FW - Oracle Utilities Framework
COBOL - Common Business-Oriented Language
XAI - XML Application Integration
JMX - Java Management Extensions
Sometimes a JVM of the coherence cluster is frozen whilst all of its applicative threads can be ok (as we can see in the table CI_BATCH_THD & CI_BATCH_RUN).
Several submitters are then on hold waiting for this threadpoolworker to update the status of their threads.
So when the threadpoolworker freeze the DB is not updated with the COHERENCE_CACHE.
We need to get a manner to keep in sync the database information (on BATCH_THD & CI_BATCH_RUN tables) with the data in the COHERENCE CACHE in the TPW.
There should be a way to have a recovery script/process that :
- checks the status of the applicative threads in the database (CI_BATCH_RUN & _THD) and
- updates the status of the threads in the coherence cluster accordingly so the submitters can be released correctly.
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