Listener Stops Dequeing The Events After Reconnect Semaphore Is Passed (Doc ID 1327919.1)

Last updated on MAY 26, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.0.0.0.1 to 7.5.0.0.0 [Release 7.0.0 to 7.5.0]
Information in this document applies to any platform.

Symptoms

After a database failure, Listener does not dequeue events after passing reconnect  semaphore successfully.

Steps to verify:

a. Loaded around 10000 events in the respective queue table (en-queued).
b. While listener is de-queuing the events simulated a DB exception:

e. All the connections are refreshed but the listener does not continue with the de-queuing of the left over events.



Cause

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