ECCResponseTimeoutException: No response for ECC message request after waiting for 300 seconds in ECC Queue

[mlobonexthink]

Hi all,

I have an issue with ServiceNow related to ECCResponseTimeoutException.

Use case: My application launches a RESTMessageV2 to get info, through MID Server, from external resource. This external resource reponds with an XML.

The problem: If the XML to get from external resource is too big, for example, 70 MB, ServiceNow raises the message below:

com.glide.ecc.ECCResponseTimeoutException: No response for ECC message request with sysid=XXXXXXX after waiting for 300 seconds in ECC Queue.

So, my questions for you are:

• Is there any way to increase that time?
• Can I change/deactivate that property? Or must to be done by some ServiceNow engineer?

Thank you for your time.

Regards,

Marcos.

[sergiu_panaite]

Hey Marcos,

The property that controls the outbound REST timeout is:

"glide.rest.outbound.ecc_response.timeout"

It defaults to 300s.

My recommendation is to just use a timeout value in outbound REST message function "waitForResponse(100)" like 100 in this example.

[vijaydodla]

I tried this one in my current code and this causing more issues because we are blocking both initiating thread and another worker thread that does REST call. In our system i'm seeing delays of more than 10 mnts for external system and i don't think i can make the thread wait for 10 mnts max because that will delay other scheduled jobs. 

Is there a way Servicenow automatically handles response when it get's it ? 

[vijaydodla]

Hi,

Were you able to resolve this issue ? How are you handling response delays in REST using ECC queue?