How can I avoid the "No response for ECC message request with sysid=xxx after waiting for 30 seconds

Aishwarya NG
Tera Contributor

Hello ServiceNow Community,

We are currently running San Diego.

and I have the following section of code in a Registration workflow

var request = new sn_ws.RESTMessageV2();
request.setHttpTimeout(360000000);

request.setEccParameter('skip_sensor', true);
request.setEndpoint(_endPoint);
request.setHttpMethod('post');
if (payload) {
payload = this.ESCAPE_CHARACTER(payload);
request.setRequestBody(payload);
}
request.setMIDServer(this.midServer);
request.setRequestHeader('Accept', 'application/json');
request.setRequestHeader('Content-Type', 'application/json');
request.setRequestHeader('Authorization', authorizationString);

var response = request.executeAsync();
response.waitForResponse(360);

 

In addition to the response.waitForResponse(360); line above, I have also added the System Property glide.rest.outbound.ecc_response.timeout with an integer value of 360 and added glide.http.outbound.max_timeout.enabled with a value false.  

But I am still receiving the error "No response for ECC message request with sysid=xxx after waiting for 30 seconds in ECC Queue".

 

Any idea why this REST API call is still timing out after only 30 seconds (instead of the 6 minutes I would expect based on the above settings)?

5 REPLIES 5

Tony Chatfield1
Kilo Patron

Hi, I would suspect the issue is 'glide.http.outbound.max_timeout'

HTTP Connection Management Properties (servicenow.com)

 

I would be raising any integration that took 30 seconds + to respond as a business risk rather than trying to work around it.

 

I have set the 'glide.http.outbound.max_timeout' to an integer value '360' and i have changed the 'glide.http.outbound.max_timeout.enabled' to 'false' but still  I'm getting the same error.

Anything else I need to change to fix this issue?

Have you tested successfully to this target platform with an external product like Postman?
This seems like an excessive delay, so maybe an issue with the target, and I would not consider it suitable for a production environment.

 

The target platform takes more than 2min I have tested it through postman. Do we have any fix to run this successfully through serviceNow?