ECS Nodes Go Down Without User Intervention When System Is Idle (Doc ID 2061128.1)

Last updated on OCTOBER 12, 2015

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version to [Release 11.2.0]
Information in this document applies to any platform.


On ECE: version,

ECS nodes go down without user intervention in following scenarios.

Scenario #1:

  1. Login to terminal and start ecc (controller).
  2. Start few processes with that controller ( pricingUpdater, ecs1, ecs2 etc.)
  3. Close the terminal directly without quitting from the controller (without typing :quit)
  4. One will see SIGHUP handler being invoked in the ecs logs.
  5. All processes started with that controller go down in the system.

Below messages appear in logs:

Scenario #2: 

ECS nodes go down randomly without any warning or error messages when system is left idle for long time.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms