Question

5
Replies
4993
Views
RakshithaS Member since 2016 9 posts
Cisco Systems
Posted: September 25, 2017
Last activity: September 27, 2017
Closed

Mapping of Incoming Response from a Connect-REST failed

---------
Hi,

We are trying a consume a REST Service through connect-REST, Whenever we are sending a huge payload in the Request, we are getting the below response and error:

When the same request(with huge payload) is sent from a REST client like POSTMAN, we are getting the right JSON response.

Response:
---------
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>414 Request-URI Too Large</title> </head><body> <h1>Request-URI Too Large</h1> <p>The requested URL's length exceeds the capacity limit for this server.
</p> </body></html>

Error:
---------
** Error mapping incoming response to <.ResponsePropertyName>: org.codehaus.jackson.JsonParseException: Unexpected character ('<' (code 60)): expected a valid value (number, String, array, object, 'true', 'false' or 'null')
at [Source: java.io.StringReader@2f7857d5; line: 1, column: 2]

However when the Request payload is small, The incoming response is rightly mapped and we can find the same on Clipboard.

We found the following solution on PDN and this didn't seem to work:

https://pdn.pega.com/support-articles/exception-thrown-incoming-response-connect-rest

The following error was seen even after implementing the work-around mentioned in the link:

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>414 Request-URI Too Large</title> </head><body> <h1>Request-URI Too Large</h1> <p>The requested URL's length exceeds the capacity limit for this server.
</p> </body></html>

Thanks in Advance!
Data Integration
Moderation Team has archived post
Share this page LinkedIn