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

Last updated on JUNE 23, 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.

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

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