Questions on Enabling OverLoadProtection
(Doc ID 2957805.1)
Last updated on JUNE 27, 2023
Applies to:
Oracle Communications BRM - Elastic Charging Engine - Version 12.0.0.6.0 and laterInformation in this document applies to any platform.
Goal
Qn1: what all the parameters and values to be kept in the charge-settings when enable overloadProtection?
Qn2: How to change threadPoolSize?
Steps:
=====
1) Open Jconsole using EMGateway or Diameter Gateway (DGW) Port.
2) In the BatchRequestService under ChargingClient -> The default value for threadPoolsize is 200.
3) When changing to the value other than 200, it changes back to 200.
Qn3: Please suggest the value for below requirements:
1) It is expecting 200 Transactions Per Second (TPS) for emGateway, it needs to give TOO_BUSY exception instead of sending it to Elastic Charging Server (ECS) if the TPS crosses.
2) It is expecting 1000TPS for DiameterGateway, it needs to give TOO_BUSY exception instead of sending it to ECS and wait in the queue if the TPS crosses 1000.
Solution
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
Goal |
Solution |
References |