BrmGateway is Unable to Process Incoming Request after JMS Server Migration in Weblogic
(Doc ID 2288086.1)
Last updated on JUNE 23, 2022
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
BrmGateway is unable to process the request after Java Message Service (JMS) server migration in WebLogic. That is, if one of the Managed Server is down, WebLogic migrates the JMS server to the next available Managed Server, but brmGateway is not able to take the change and is throwing exceptions. After a restart of brmGateway, it is responding ok.
Error snippet from ecs.log (elastic charging server log):
1. Consider a clustered WebLogic setup with 3 managed server nodes.
2. Shut down one managed server in the cluster.
3. Send topup requests for example to Elastic Charging Engine.
4. Check brmGateway log, it would have exceptions connecting to the JMS queue.
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