Last updated on MAY 17, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 22.214.171.124.0 to 126.96.36.199.0 [Release 7.5.0]
Information in this document applies to any platform.
BI Publisher 11g causes BRM 7.5 to hang after receiving a corrupt XML.
During Electronic Billing Presentment(EBP), when BRM starts to send invoices to BI Publisher(BIP), if BIP gets a corrupt 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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms