My Oracle Support Banner

JMS Connection Issues Logged In Severity "DEBUG" Instead Of "WARNING" (Doc ID 2271279.1)

Last updated on MARCH 25, 2019

Applies to:

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

Symptoms

On : 11.3.0.1.1 version,

If there is any JMS connection issues, it is getting logged as DEBUG instead of WARNING


Expected Behavior:

It means that, when you configure the log4j in production mode (i.e. non-DEBUG), these problems will not be visible in the log.

These log messages should be changed to warning.

Changes

 

Cause

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
Symptoms
Changes
Cause
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.