The system property controls the maximum amount of time, in seconds, to wait for a response when sending an outbound REST message via the ECC queue (e.g. when using Mid server). Changes to this property will not take effect until your instance is restarted.

Steps to Reproduce


- You have a working REST message with a MID Server set
- You have a MID Server working fine
- The REST call should take more than 1 minute.

1. Set to a 10  (seconds)
2. Send an outbound RESTMessage via the ECC queue to your REST Provider

var sm = new sn_ws.RESTMessageV2(SLOW_REST_MESSGE,"get");
var response = sm.executeAsync();

Expected: Your request will timeout in 10 seconds

However the following is error is received

2017-02-02 04:59:01(566) worker.2 worker.2 SEVERE *** ERROR *** com.glide.ecc.ECCResponseTimeoutException: No response for ECC message request with sysid=xxxx after waiting for 300 seconds in ECC Queue...

It times out after the original timeout (e.g. 60 secs)

NOTE: You should not use the RESTResponseV2.waitForResponse(time) API, because that will override the property.


This problem was fixed in Kingston. On older releases, if you set the record on sys_properties named to any value, you will need to restart your instance.

Alternatively, use the "waitForResponse" property to overwrite the value on the REST message call.


var sm = new sn_ws.RESTMessageV2(SLOW_REST_MESSGE,"get");
var response = sm.executeAsync();

Ref. documentation:

Istanbul - RESTResponseV2 - waitForResponse(Number timeoutSecs)

Kingston - RESTResponseV2 - Scoped, Global

Kingston - Asynchronous RESTMessageV2 example

Related Problem: PRB851448

Seen In

There is no data to report.

Fixed In


Associated Community Threads

There is no data to report.

Article Information

Last Updated:2019-05-21 11:36:45