E-IB: Outbound REST http 500 Error JSON Formatted Response Results in "HttpTargetConnector: problem parsing xml response"

(Doc ID 2244805.1)

Last updated on OCTOBER 03, 2017

Applies to:

PeopleSoft Enterprise PT PeopleTools - Version 8.53 to 8.55 [Release 8.4]
Information in this document applies to any platform.

Symptoms

Issue Statement:
******************************
Customer is testing an outbound REST web service.
If the 3rd party fails to process the request due to a server error, it sends back an http 500 status code, along with a JSON formatted error message.

When this happens, integration Broker fails to parse the response, and throws an exception.


Environment
********************
PT 8.55.03, Application/version?

Error:
***********************************

HttpTargetConnector: problem parsing xml response:

Call stack
com.peoplesoft.pt.common.XmlException: [Parsing error] msg: Fatal Error: at file null line: 1 column: 1 message: Content is not allowed in prolog.
at com.peoplesoft.pt.common.XmlDocument.parse(XmlDocument.java:144)
at com.peoplesoft.pt.common.XmlDocument.ParseXmlFromString(XmlDocument.java:222)
at com.peoplesoft.pt.integrationgateway.targetconnector.HttpTargetConnector.send(HttpTargetConnector.java:958)
at com.peoplesoft.pt.integrationgateway.service.BasicConnectorInvocator.execute(BasicConnectorInvocator.java:131)
at com.peoplesoft.pt.integrationgateway.framework.GatewayManager.invokeService(GatewayManager.java:148)
at com.peoplesoft.pt.integrationgateway.framework.GatewayManager.connect(GatewayManager.java:192)
at com.peoplesoft.pt.integrationgateway.listeningconnector.PeopleSoftListeningConnector.doPost(PeopleSoftListeningConnector.java:186)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:751)
at com.peoplesoft.pt.integrationgateway.listeningconnector.PeopleSoftListeningConnector.service(PeopleSoftListeningConnector.java:87)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:844)



Steps To Reproduce:
**************************

1. Create the custom REST service, and write the PeopleCode
2. Execute the outbound request so it triggers an http 500 status code, and a JSON formatted error message by the 3rd party.


Cause

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