Question

3
Replies
2030
Views
Mustafa Jamil (mustjam1)
Cognizant

Cognizant
US
mustjam1 Member since 2013 4 posts
Cognizant
Posted: September 1, 2017
Last activity: September 5, 2017
Posted: 1 Sep 2017 7:06 EDT
Last activity: 5 Sep 2017 1:33 EDT
Closed

Socket timeout error on Connect REST

We are trying to invoke a rest API from UAT but the API is inaccessible due to firewall restrictions. While the appropriate team sorts this out, we have the requirement to show a meaningful message. e.g. System unavailable or timeout etc. We have timeout of 5000 ms defined in the rest rule but it is not working in this scenario.

Right now when invoked, the system is freezing and gets hung. The log is full of requestor locked and socket timeout exceptions before finally throwing a connection refused message after few minutes . Please advise how to show the terminate the rest connection and show a meaningful message and not let the system clok in front of the user. Logs attached.

Data Integration
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.