- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-05-2020 04:27 AM
Hello ServiceNow Community,
We are recently upgraded to Orlando version, when i am testing REST method i am getting below error.
"No response for ECC message request with sysid=6f4362af1b9a5850060d54662a4bcbca after waiting for 60 seconds in ECC Queue"
I have verified the same error in community i found below kb article. i could not find this "glide.http.outbound.max_timeout" property to set the value.
https://hi.service-now.com/kb_view.do?sysparm_article=KB0744311.
Could someone help on this issue?
Solved! Go to Solution.
- Labels:
-
Orchestration (ITOM)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-10-2020 05:03 AM
So that property that you mentioned will have to be added it's not there by default more then likely. Just note that will increase it for all REST calls. I would try to do this REST call using a rest client of some sort and see if it takes that long to come back. 1 minute for a REST call to response seems like a long time (essentially the error message is saying there was an output entry that was processed but no input was seen within 1 minute which means the REST call hasn't returned properly).
I would also check the MID server to make sure it's not over utilized if you are using one for the call.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-05-2020 04:36 AM
Hi,
How are you doing this? using REST Activity in workflow?
Thanks,
Ashutosh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-10-2020 04:14 AM
Hi,
No it is not REST activity, When i am trying to hit the Oracle Endpoint using REST Method.
Regards
Suhasini
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-10-2020 05:03 AM
So that property that you mentioned will have to be added it's not there by default more then likely. Just note that will increase it for all REST calls. I would try to do this REST call using a rest client of some sort and see if it takes that long to come back. 1 minute for a REST call to response seems like a long time (essentially the error message is saying there was an output entry that was processed but no input was seen within 1 minute which means the REST call hasn't returned properly).
I would also check the MID server to make sure it's not over utilized if you are using one for the call.