The Connection to CM Through CMMP Occasionally Fails when One or More of the CMs in the CMMP Pool is Down (Doc ID 1614989.1)

Last updated on SEPTEMBER 24, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.0.0.0 and later
Information in this document applies to any platform.
***Checked for Relevance on 13th August 2015***

Goal

This article explains why the connection to a Connection Manager (CM) through a Connection Manager Master Process (CMMP) can fail if one or more of the CMs from the CMMP pool is down. It answers the question if - beyond its load-sharing feature - it is possible to use CMMP to implement a fail-over mechanism.

Example :

Considering a system which CMMP has two connections CM1 and CM2 in its pool; CM1 runs normally and CM2 is in a failed state. One session could run testnap which will only be connected from time to time. The load balance scheme is random :

Statistically, there is a 50% chances to hit the failed CM, 50% chances that the connection properly works.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms