Debug Log Level For DGW Enabled With JMX Update Is Not Taking Effect (Doc ID 2241184.1)

Last updated on MARCH 16, 2017

Applies to:

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

Goal

On : 11.3.0.1.0 version, Diameter Gateway (DGW)

Issue:

Post restart of DGW, if there is a JMX update to increase or decrease the log level, it does not work. If one usage request is sent from DGW to ECE and then performing the JMX update, then it is working.

Steps for non-working scenario:

- Make sure all ECE and DGW processes are up with minimal log level.
- Restart DGW
- Do JMX update to increase the DGW log level. This step does not increase the log level.


Steps for working scenario:

- Make sure all ECE and DGW processes are up with minimal log level.
- Restart DGW
- Pass a usage request from seagull.
- Do JMX update to increase the DGW log level. This step does increase the log level. So it seems like only post usage, one is able to increase the log level.

Solution

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