My Oracle Support Banner

The SOAP Faultcode and Faultstring Information Not Propagated Properly to Application (Doc ID 1072049.1)

Last updated on DECEMBER 20, 2017

Applies to:

Oracle Communications Services Gatekeeper - Version: 4.1.1 and later   [Release: 4.1 and later ]
Information in this document applies to any platform.
Checked for relevance on 08-Dec-2011

Symptoms

For SOAP2SOAP plugin, OCSG 4.1.1 does not propagate the SOAP fault information properly. The field faultcode is populated incorrectly, whereas faultstring is not populated at all. Below is the example response received:

<env:Fault>
<faultcode>env:Server</faultcode>
<faultstring/>
<detail>
<exam:InsufficientFundFault xmlns:exam="http://example">
<exam:balance>111</exam:balance>
<exam:requestedFund>222</exam:requestedFund>
</exam:InsufficientFundFault>
</detail>
</env:Fault>

Besides, the undefined exception is not transferred transparently.

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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.