Managing CM Connections Load Balancing Using F5
(Doc ID 2693908.1)
Last updated on JULY 27, 2020
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
An user has tested F5 load balancer between a client application and Billing and Revenue Management (BRM). It worked as expected, the application’s connection pool had connections to both connection managers (CM).
- A solution is still needed for the re-balancing issue.
If the application’s connection pool already has a sufficient number of connections for the current load, it will reuse them.
If a CM was down and then became available again, the application will start using it again only if the load is increased or some connections went idle and were removed from the pool.
- Is there a way to force a connection to be removed from the connection pool even if it never goes idle?
It is something like expiration time, so a connection can live only a specified amount of time.
In this case, some connections would be removed from the connection pool even if the load has not changed and the application could get a new connection from the load balancer.
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