OSB not able uncompress the message from business service when the HTTP status code is 500
(Doc ID 2317640.1)
Last updated on MAY 10, 2023
Applies to:
Oracle Service Bus - Version 12.2.1.2.0 and laterInformation in this document applies to any platform.
Symptoms
On : 12.2.1.2.0 version, OSB Transports
OSB not able to parse Item webservice fault message
we have one Oracle service bus project where the Business Service(AnySOAP) calling the below Item Cloud service WSDL with proper credential.
https://eejx-dev1.scm.us2.oraclecloud.com:443/egpItems/ItemServiceV2?wsdl
Attached the zip consisted the wsdl and related xsds.
Normally for success case we are getting proper response like below
<ns0:updateItemResponse
<ns2:result
<ns0:Value
...
But in case of Business error in SOAPUI though we are getting below error
But in Service bus Business service we are getting below error
OSB-380000: [OSB-381304]Exception in HttpOutboundMessageContext.RetrieveHttpResponseWork.run: java.lang.RuntimeException: com.bea.wli.sb.service.handlerchain.HandlerException: Couldn't create SOAP message due to exception: XML reader error: com.ctc.wstx.exc.WstxUnexpectedCharException: Illegal character ((CTRL-CHAR, code 31))
at [row,col {unknown-source}]: [1,1]
java.lang.RuntimeException: com.bea.wli.sb.service.handlerchain.HandlerException: Couldn't create SOAP message due to exception: XML reader error: com.ctc.wstx.exc.WstxUnexpectedCharException: Illegal character ((CTRL-CHAR, code 31))
at [row,col {unknown-source}]: [1,1]
Attached Request and response payload for reference.
Request to check why OSB business service not able to properly parse fault message in case of Business fault.
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 |