Issue In Changing Hostname Via Jconsole
(Doc ID 2788603.1)
Last updated on AUGUST 10, 2023
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
Facing issue after changing the originHost parameter from Jconsole.
Steps to reproduce the Issue:
1. Connect the Jconsole with the JMX enabled Node
2. Expand ECE Configuration -> charging.diameterGatewayConfigurations.diameterGateway -> Attributes
3. Change the originHost
4. After changing the OriginHost from "HOSTNAMEOLD" to "HOSTNAMENEW".
5. The value is changed succesfully in Charging-setting.xml and Appconfiguration
When the Usage is triggered using Seagull with the update Originhost , the Credit-Control Answer (CCA) is sent back to Old OriginHost.The same request is triggered post Diameter Gateway (DGW) restart the CCA is sent to correct host.
Query: Why DGW bounce is required when parameter is changed from the Jconsole?
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