EMGateway Error
(Doc ID 2542255.1)
Last updated on DECEMBER 28, 2023
Applies to:
Oracle Communications BRM - Elastic Charging Engine - Version 11.3.0.6.0 and laterInformation in this document applies to any platform.
Goal
An error is observed with the emGateway:
2019-01-21 18:05:10.241 CST ERROR - - - - EMGatewayBundle-18201: Error in client thread : oracle.communication.brm.charging.migration.customer.updater.CustomerUpdaterException: oracle.communication.brm.charging.messages.update.MessagesUpdateException: MessagesUpdateMessagesBundle-7005: BalanceElement with Numeric Code 188 Not Found.
at oracle.communication.brm.charging.migration.customer.updater.internal.converter.BalanceImpactConverter.buildBalanceUpdateRequest(BalanceImpactConverter.java:201)
at oracle.communication.brm.charging.migration.customer.updater.internal.converter.AccountAdjustmentEventConverter.convertEvent(AccountAdjustmentEventConverter.java:95)
at oracle.communication.brm.charging.migration.customer.updater.PayloadConverter.convertPayload(PayloadConverter.java:119)
There are different EMGateway configured to receive different BRM requests (billing, account creation, payments, balance query, and prepaid, etc.) in the ECE Cluster. In the time lapse where the error was occurring, the WebService team was running performance tests to BRM-ECE for balance query requests, this requests uses the emGatewayPrepaid to be attended by ECE, but for some reason also the emGatewayUsers (used for process payments) and the other emGateways was reporting timeouts in the answer to BRM.
ecs1.log:
2019-02-26 10:21:20.802 CST ERROR - - - - ProcessorFrameworkMessageBundle-17000: Unexpected exception: java.util.concurrent.TimeoutException: Server Timeout while processing Update Request after - 217407 (msec)
After the resource assignation finished, with a manual rolling upgrade of all charging nodes, the error is no longer persist.
As recommended, overload protection for ECE clients that process usage requests should be set to true before GoLive, like the Diameter Gateway and OCOMC.
Question: Is it also necessary and/or recommended to set this configuration on for EmGateway?
Would this parameter do something in EmGateway?
If recommended, is there an alternative way to turn-on besides the JMX port every time that the client starts? For example, in a configuration file?
Any recommendation for setting the AcceptablePendingCount parameter?
Solution
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
Goal |
Solution |
References |