BI Publisher 11g Causes BRM 7.5 Hang After Receiving Corrupted XML
(Doc ID 1595115.1)
Last updated on AUGUST 28, 2023
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 to 7.5.0.0.0 [Release 7.5.0]Information in this document applies to any platform.
Symptoms
BI Publisher (BIP) 11g causes Billing and Revenue Management (BRM) 7.5 to hang after receiving a corrupted XML.
During Electronic Billing Presentment (EBP), when BRM starts to send invoices to BIP, and if BIP gets a corrupted XML from BRM, it raises XMLParseException and puts the job into Failed state. Although there are proper XMLs in the same chunk, all proper invoices are discarded. Meanwhile this failure of job is reflected to BIP GUI but BRM is not informed, so it hangs in running state, as docgen.sh hangs or crashes.
This case was tested in all environments by breaking an invoice's XML format, and same consequence is observed.
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 |