JMS Connection Issues Logged In Severity "DEBUG" Instead Of "WARNING"
Last updated on JUNE 23, 2017
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.
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