OC3C is not Maintaining Connections to BRM
(Doc ID 2422635.1)
Last updated on MARCH 19, 2019
Applies to:Oracle Communications Convergent Charging Controller - Version 6.0.1 and later
Information in this document applies to any platform.
On Oracle Communication Convergent Charging Controler (OC3C) SLEE is not able to maintain the number of connections to Billing and Revenue Management (BRM).
We have the following scenario:
There are 2 SLEE nodes and 4 BRM nodes. Initially the 2 SLEE nodes were connected to port 11461 on all of 4 BRM nodes, so on each BRM node customer had 80 connections on Connection Manager (CM) port 11461.
After a month, the connections had dropped to just over 50 on each node, hence customer created one more CM(port 11462) and connected SLEE node1 to CM port 11461 and SLEE node 2 to CM port 11462 in order to maintain 80 connections to BRM.
After some time a drop in connections was seen only from SLEE node 2.
The expected behavior is to maintain 80 connection per port to BRM.
Issue is happening in production and data roaming sessions are being impacted resulting in dropped sessions and revenue loss.
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