EMA: Flood of 'Request timed out'

Frederic

The RTO C++ EMA application are receiving more than 200MB the status message 'Request timed out' in seconds. How to cope with such case? e.g., tune some configurations? or due to some network issue? The client is using an EMA application (in docker) to connect to the RTO behind a firewall. It suddenly turns into this issue. So I would like to know if we may mitigate that via some suggestions.

StatusMsg

streamId="446350"

domain="MarketPrice Domain"

state="Open / Suspect / Timeout / 'Request timed out.'"

name="QUX2"

serviceId="257"

serviceName="ELEKTRON_DD"

StatusMsgEnd

umer.nalla

Hi @Frederic

All the status messages above show that the data streams are still open - but suspect - which would indicate the connection is still considered active - but not responding in a timely manner.

Did you raise a ticket with the RTO team to confirm if there were any issues around the time of the above event and/or if they can check the RTO logs for the application's connection - to help explain the timeout?

Has the above happened on several occasions or just a single incident?

Can you confirm how many instruments (RICs) the above application is requesting? If a high number of instruments, does the application throttle the requests or request them all in a tight loop without any pause?

Did the above application eventually recover and receive data for the instruments?

It could be the RTO is not coping with the number of requests your application is making in a timely manner (OR the application is a 'Slow Consumer' and is not able to process all its data in a timely manner).

What could be reason of receiving STATE like [Open / Suspect / None / 'Request timeout'] Using EMA? - Forum | Refinitiv Developer Community

The application could try and increase the timeout as described in the post:

[EMA C++]How to set RequestTimeOut in EmaConfig.xml - Forum | Refinitiv Developer Community

But this may only provide temporary relief - for short periods of high volume.

Frederic

Also this type of Status message (on same RIC):

StatusMsg

streamId="24948"

domain="MarketPrice Domain"

state="Open / Suspect / None / 'Service for this item was lost.'"

name="7#CL:"

serviceName="ELEKTRON_DD"

StatusMsgEnd

Frederic

https://community.developers.refinitiv.com/discussion/comment/87385#Comment_87385

Many thanks for the advices. I will ask the client to revise the code based on the coding principles mentioned above.