My Oracle Support Banner

ECE Dual Site Cannot Be Started In OC-CNE Because Of Changed Cluster.local (Doc ID 2858717.1)

Last updated on MARCH 28, 2022

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version 12.0.0.4.0 and later
Information in this document applies to any platform.

Goal

On : 12.0.0.4.0 version, Charging server launcher

Its reported earlier that ECE might be not working well when in OC-CNE cluster name is changed from “cluster.local” to a specific name, e.g. abcde-fg.
 
Until now user didn’t fully understand the consequences of this change but when team was trying to start dual-site setup it became obvious that ECE tries to listen for JMX ports on .cluster.local i.e. uses the following (hardcoded) JVM parameter -Djava.rmi.server.hostname=ecs1-0.ece-server.pp-ece-app.svc.cluster.local.
 
Would it be possible to provide a solution? i.e. an alias for cluster.local?
 

NOTE: Below snippet from ECE startup.sh showing HOSTNAME_FQDN with hardcoded cluster name. It’s not possible to override it by a configuration.
HOSTNAME_FQDN=$HOSTNAME"."${ECE_SERVICE}"."$NAMESPACE".svc.cluster.local"
 

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.