JMS Connection Issues Logged In Severity "DEBUG" Instead Of "WARNING"
(Doc ID 2271279.1)
Last updated on FEBRUARY 24, 2021
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
On : 18.104.22.168.1 version,
If there is any JMS connection issues, it is getting logged as DEBUG instead of WARNING
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.
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