Experiencing Error while Getting Response from Mulesoft as "Client connection was closed"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-05-2022 12:23 PM
We are having Mulesoft as the middleware between our Service-Now and external systems but off late we are getting below error in the PROD environment for x-status-api, actually all the transactions were successful but it seems ServiceNow is releasing the session in few seconds after making a request to MuleSoft that’s why when MuleSoft is trying to handover the response back to ServiceNow then it is not able to find any active session and throws an error. Can you please look into this and let us know why ServiceNow is releasing the sessions.
This the error we are experiencing :
"Client connection was closed "
Also it would be better if anyone can help to let us know where in Service-Now we can find the Outbound Rest Timeout Configuration. We can try increasing the timeout period if in case that can resolve this Issue.
- Labels:
-
IntegrationHub

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-05-2022 07:04 PM
Hi Saurabh,
Members of the community are not able to look into other's instance. Should contact NOW Support to get assistance.
Outbound rest timeout is glide.http.outbound.max_timeout
Check the following page for more properties.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-05-2022 07:06 PM
Following Now Support page has Best Practices on settings.
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0694711