My Oracle Support Banner

ECE Notification Which Failed In BRM Is Kept Resending And Blocks Jms Topic (Doc ID 2579204.1)

Last updated on AUGUST 28, 2019

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version 11.3.0.7.0 and later
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR
---------------
Elastic Charging Engine (ECE) notification which failed in BRM is attempted to resend repeatedly and blocks JMS topic. In more detail, there is ECE lifecycle notification which is sent to Billing Revenue Management (BRM) in order to update service state, however this request fails in BRM. The message with notification (which already failed) is resent one more time and stuck in JMS topic, blocking other messages in the queue. The problem can be solved by BRM Gateway restart, however after some time the failing request is resent and again it blocks queue.

Problem:

1) Why are notifications which failed in BRM are resent by ECE?
2) Why are messages stuck in JMS queue and brmGateway is required to empty it?


STEPS
-----------------------
The issue can be reproduced at will with the following steps:

Scenario 1:

1. Created an account
2. Then shut down the Connection Manager (CM)
3. Generated LIFECYCLE_TRANSITION_NOTIFICATION_EVENT to change life cycle status from pre-active to active
4. Notification remained in JMS Queue since CM is down
5. Then copied and modified the JMS message using export and import option in queue. Modified public identifier, customer ID, JMS message ID and this customer does not exist in the system
6. Then brought up the CM
7. After couple of minutes, brmGateway consumed the messages, one message processed successfully and the second fault message was moved to suspense queue
8. After some time, the fault message disappeared from the queue


Scenario 2:

1. Created an account
2. Then shut down the CM
3. Generated LIFECYCLE_TRANSITION_NOTIFICATION_EVENT to change life cycle status from pre-active to active
4. Then did external top-up
5. Both the notifications stayed in JMS Queue since CM is down
6. Then waited for 30 minutes so that brmGateway times out
7. Then brought up the CM and generated two more top-up messages
8. All the messages were in the queue and were not consumed. Even the new messages were not consumed
9. All the messages were consumed after the brmGateway restart

Cause

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
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.