Pipeline Did Not Stop or Reconnect when It Lost Connection to DB
(Doc ID 1480014.1)
Last updated on DECEMBER 05, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 7.3.0 to 7.5.0]
1. When Pipeline framework connection to database is lost, it continues working. From that moment, EDRs are potentially wrong rated because of customer data not updated. Other consequence, it's not possible to receive/answer requests for account locking from Rerating.
From process log file, observed that after ERR_DEQUEUE_EVENT shown below, no INF_EVENT was logged.
Expected behaviour is the Pipeline to automatically reconnect or to stop.
2. When database connection was lost, sending a semaphore to reconnect did not work.
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