Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

JsonParseException : Error mapping incoming response

SA-21642

Summary



An exception was thrown when incoming response for Connect-REST was parsed.

Error Messages



Error mapping incoming response to .<<propertyName>>: org.codehaus.jackson.JsonParseException: Unexpected character ('<' (code 60)): expected a valid value (number, String, array, object, 'true', 'false' or 'null')
at [Source: [email protected]; line: 1, column: 2]

Steps to Reproduce



Call a REST service, and map the response data in Connect-REST.

Root Cause



A third-party product issue:
After adding DEBUG to pyInvokeRestConnector activity, the following HTTP response in XML was returned by the REST service endpoint:


<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL / env/test/search/memberId was not found on this server.</p>
</body></html>

When parsing this XML response, JSON parser threw the exception. The HTTP 404 message in the reponse clearly states that resource is not availble because the REST endpoint URL in the Connect-REST rule is not correct.


Resolution



Perform the following local-change:
Mention the correct REST endpoint URL in the Connect-REST rule.
Suggest Edit

Published April 1, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us