Question
Wells Fargo
IN
Last activity: 31 Mar 2016 5:51 EDT
Connect REST - "Caught unhandled exception: java.net.SocketTimeoutException: Read timed out", when used Content Type "application/x-www-form-urlencoded"
Connect REST - "Caught unhandled exception: java.net.SocketTimeoutException: Read timed out", when used Content Type "application/x-www-form-urlencoded".
When I use any other content types, then able to communicate with the Service but getting error response.
PFA attached error log for more information on the exception trace.
Version: Pega 7.1.7
Content type was set in REST POST method headers as below
Name - "Content-Type"
Description - Content Type
Map From - Constant
Map from key - "application/x-www-form-urlencoded"
There is no request body, just one static value passing as part of URL, and 2 more params passing through "POST header query string params" (I think these 2 are specific to the content type, because when I remove these 2 params getting error response from SOAP UI)
Please help me resolving this issue.
Regards,
Rajesh
Accepted Solution
Wells Fargo
IN
Pega Support provided a solution for this, and it is working fine now. No Hotfix is required.
It's just a change in the way we are passing few parameters which are not part of the Request/Header. I think the parameters are specific to the Content Type "application/x-www-form-urlencoded".
In the Message data section, configured "Constant" instead of "JSON", and in MapFrom Key field given the content type parameters.
Pegasystems Inc.
US
Not sure if this will resolve your issue but worth trying: https://community.pega.com/knowledgebase/release-note/service-responses-http-and-rest-connectors-are-no-longer-modified. Test it out in a pega 7.1.8+ system if possible, if the error goes away, then you know that is something pega has fixed.
Wells Fargo
IN
Thank you for your response Kevin, right now our application is in 7.1.7 in Live, so this needs to be resolved in 7.1.7. But, will give it a try in 7.1.8+, if possible, so that atleast we would come to know this is fixed in later versions and can request Pega Support for a Hotfix.
Thanks,
Rajesh
Accepted Solution
Wells Fargo
IN
Pega Support provided a solution for this, and it is working fine now. No Hotfix is required.
It's just a change in the way we are passing few parameters which are not part of the Request/Header. I think the parameters are specific to the Content Type "application/x-www-form-urlencoded".
In the Message data section, configured "Constant" instead of "JSON", and in MapFrom Key field given the content type parameters.