Exceptions Occurring In Webservice Pcm.Jar Are Not Handled Properly

(Doc ID 953204.1)

Last updated on JULY 28, 2017

Applies to:

Oracle Communications Billing and Revenue Management - Version and later
Information in this document applies to any platform.


Problem Statement:
Exceptions thrown in webservice pcm.jar are not handled properly and are causing Java NULL pointer exceptions which is creating lots of issues in integration.
For instance, if the webservice pcm.jar is unable to find the field that comes in the XML input, it throws NULL pointer exception.

soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:ns1="http://xml.apache.org/axis/">ns1:Server.userException</faultcode> <faultstring>java.lang.NullPointerException</faultstring>
at com.portal.pcm.EBufException.<init>(Unknown Source)
at com.portal.pcm.EBufException.<init>(Unknown Source)
at com.portal.pcm.FList.createFromXML(Unknown Source)
at com.portal.webservices.OpcodeCaller.opcodeWithFlags(OpcodeCaller.java:94)
at com.portal.webservices.OpcodeCaller.opcode(OpcodeCaller.java:59)

Any exception occurring in the webservice pcm.jar before hitting the BRM should be caught/handled and proper response should be returned. The expectation is the error response should be similar to the 'response for BRM OOB error'. i.e. it should have the proper error code and other details in it.




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