How Does The BRM JCA Adapter React When CM Fails
(Doc ID 1534738.1)
Last updated on FEBRUARY 24, 2021
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 7.4.0 to 7.5.0]
Information in this document applies to any platform.
Q&A on JCA Adapter behaviors when CM fails.
Given a Java 2 platform Enterprise Edition (J2EE) compliant application connecting to multiple Billing and Revenue Management (BRM) servers through the J2EE Connector Architecture (JCA); for instance an environment running :
The JCA connects to the BRM Server through the parent Connection Manager (CM), which itself spans multiple child cm processes to handle the connections from JCA.
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
|Questions and Answers|
|What is the behavior of the JCA adapter when the cm process it is connected to fails?|
|What happens if JCA sees one CM from the pool unavailable?|
|What happens if the selected cm is not able to properly complete the requested operation?|
|What happens if a cm process dies in the middle of an operation?|