What could be reason of receiving STATE like [Open / Suspect / None / 'Request timeout'] Using EMA?
We are getting STATE like [Open / Suspect / None / 'Request timeout'] continuously for certain ITEMs, But for other items we do get response and no issue. It seems EMA does not return back anything for these items. Is there anything we need to take care from our side?
Best Answer
-
Hello @gaurav.mahajan
EMA Java sends Open / Suspect / None / 'Request timeout' to the application when it does not receive the refresh message (the first data message) of the requested item from the server within the request timeout (default is 15 seconds). It seems the default timeout, 15 seconds, is not long enough for the server to send the refresh of requested items to your application.
The request timeout in EMA Java is defined by the Consumer’s parameter named RequestTimeout(in milliseconds). The parameter is explained in [Elektron-SDK Java]\Ema\Docs\EMAJ_DevGuide.pdf shown below:
Please set RequestTimeout to be the longest timeout which you can accept to wait for a refresh message of a requested item. For example to set it to be 120 seconds which is 120000 milliseconds in a Consumer node named "Consumer_1"(default Consumer node):
<Consumer>
<Name value="Consumer_1"/>
...
<RequestTimeout value="120000"/>
</Consumer>If the problem still occurs after increasing RequestTimeout , the server side should be investigated why it does not send the refresh messages back or why it spends too long time to process items/sends refresh messages back. Please contact your server’s administrator or Thomson Reuters Account team if the server side is owned by Thomson Reuters to investigate/fix the server side.
If your server’s administrator/you require any help about
Thomson Reuters products which are on your server side e.g. TREP(ADS/ADH), EZD,
Elektron Edge. Please submit the query
to the product support team who can assist you on this via https://my.thomsonreuters.com/ContactUsNew At “Select product”, please select the product which you requires help e.g. ADS-Advanced Distribution Server for ADS, Thomson Reuters Elektron Connect for EZD.1
Categories
- All Categories
- 6 AHS
- 39 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 370 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 60 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛