Issues in Tracing Configuraiton File in ECE
Last updated on MAY 14, 2018
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
There is any error in execution of updateSubscriberTraceConfiguration and the jconsole is not reporting the same. The error is visible in logs. So after invoking the updateSubscriberTraceConfiguration procedure every time there is a need to go and check the logs for the confirmation.
The behavior is not correct, because we use the log to debug the error, but application has to tell the end-user whether it has run successfully or not. If not then there is a need to go to the logs for debug.
Diameter Gateway log :
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