Open / Suspect / None / 'Request timeout'
Best Answer
-
Hello @chenjihui
The proper RequestTimeout depends on the network and infrastructure. How long they spend the time to send, process all item requests and send all data back to your application. To know the proper timeout value, you should find out the longest time to get data. I suggest you do the following:
1. Set RequestTimeout to be 0. EMA will wait for a response indefinitely.
2. Turn on EMA trace log. EMA traces its received and sent messages from/to the infrastructure with the timestamp in XML format to stdout/console. To enable EMA trace log set XmlTraceToStdout in Consumer Node to be 1. For example:
<Consumer>
<Name value="Consumer_1"/>
…
<XmlTraceToStdout value="1"/>
</Consumer>3. Run your application with redirect the output to a file to keep EMA trace log in the file.
4. Find out which request spends the longest time from EMA trace log.
For example, RIC TRI.N spends the longest time as shown below:
- The item request is sent at 10:48:27:
- The data is received at 10:48:57:
The longest time is 30 seconds. Hence, you should set RequestTimeout + spare time e.g. 35 seconds or 35000 set in RequestTimeout. This is to make sure that your application will get all data instead of 'Request Timeout' error.
Hope this help.
0
Answers
-
-
Hello @chenjihui
Does your application use EMA C++ or Java?
0 -
use EMA java
0 -
Hello @chenjihui
If you still get 'Request timeout' and RequestTimeout parameter is very long e.g. 300000 (5 minutes), the network and the infrastructure should be investigated. Therefore, you should contact your network team and your infrastructure team or the account team who owns the infrastructure.
0
Categories
- All Categories
- 6 AHS
- 39 Alpha
- 162 App Studio
- 4 Block Chain
- 4 Bot Platform
- 17 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 中文论坛