EMA J - RTO reconnect
Good afternoon,
I am building an AWS client based on EMA J 3.7.3.0, specifically consumer113 (example code). The application is connecting to the RTO service. Both my code and Refinitiv's consumer113 have been experiencing trouble
1. Making an initial connection - quitting after 45000 milliseconds/5 attempts
2. Staying connected more than 15 minutes, after which there is not attempt to reconnect.
3. I was led to believe by Refinitiv technical staff that EMA J ensured automatic-reconnections but I can now see this is not the case and I will have to build logic to address this (maybe consumer113 is too basic)?
I have done some digging around the forums and found references to a thread that has to be run to keep the connection up.
Could you please advise and help? Thank you!
Best Answer
-
Thank you for reaching out to us.
You need to test it on the local environment to make sure it can run properly on the local environment. It should be the network policies on AWS.
Then, please check the version of authentication (v1 or v2) that you are using by refering to this article.
If you are using the v1 authentication, the v1 credentials can't be used concurrently with other applictions.
You can also enable trace logging in the EMA to verify what the problem. To enable logging, please refer to the Learn how to direct EMA Java log to Java Logging API article.
0
Answers
-
Thank you Jirapongse. I turned on full-logging but the mystery persisted. In the end the issue was the length of the sleep the thread during which all the action happens. It was timed to 15 minutes. The thread sleeps while the main consumer reacts to messages from the server. I put a Thread.sleep(60000) (1 minute) in an infinite loop at the bottom of main(...) - while (true) { Thread.sleep(60000) } . I suppose I could have lengthened the sleep time. Maybe longer is better? This comes from from Gurpreet's answer here https://community.developers.refinitiv.com/questions/21086/data-streaming-auto-logout-login-stream-was-closed.html
0 -
The while (true) { Thread.sleep(60000) } is enough to verify if the application can connect to the server.
0
Categories
- All Categories
- 6 AHS
- 37 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
- 367 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
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛