Re-Login with E-SDK 1.5.0L1 Java on ERT Connection
Hi I am developng an Java EMA application in order to consume data from ERT. The service discovery and Item registration works fine, but after 300 seconds I get kicked out.
I cannot find in the documentation the proper way (in Java) to renew the login token. I have the Login message received containing the first token and the (Unix) time when it will expire but I do not know what to do with this. How do i send a new LoginReq? What shoud be contained? The user/password/appId or the old token?
I have experimented with the consumer example 430, but the consumer.reissue call leads to a NullPointer exception.
Does anyone have a working example for this?
Thanks and kind reagrds
Frank
Best Answer
-
Hello @f.heuschen
It is possible that EMA does not receive new token from EDP gateway e.g. network issue or EDP gateway sends new token too late when TREP authentication token has expired already. By default, EMA requests a new access token by multiplying the token’s published timeout by 0.8 which is every 4 minutes(token expire in 5 minutes) according to TokenReissueRatio parameter of Consumer. Hence, EMA requests token once before the token expires. Please try to increase the number of request token by adjusting TokenReissueRatio parameter e.g. 0.3(try to request token 3 times within in 5 minutes).
If the problem still occurs even adjusting TokenReissueRatio parameter, please contact ERT in Cloud support team who can help you to investigate the server side by opening the ticket via Product Support | MyRefinitiv . Select Product as Elektron Real Time in Cloud.
0
Answers
-
Hello @f.heuschen
EMA sends the refresh token to proactively obtain a new access token prior to the published expiration timeout(300 seconds) to keep the ERT connection. Hence, the application does nothing about re-login as shown in the figure below:
For more details, please refer to section 6.3.3 Refreshing the Access Token and Sending a Login Reissue in EMA Java Developers Guide
You can try example450__MarketPrice__QueryServiceDiscovery to consume data from ERT. Please refer to EMA Quick Start - Connecting to Elektron Real Time in Cloud for more details to run the example.
0 -
Hello @Pimchaya.Wongrukun
many thanks for your answer. Actually I have based my application on example450__MarketPrice__QueryServiceDiscovery and it works fine. Nevertheless, yesterday the application ceased to receive updates and in the log I found:
RDMLogin stream was closed with status message
username (some lenghty string)
usernameType 1State: Closed/Suspect/Timeout - text: "TREP authentication token has expired."
loggerMsgEndWhich led me to believe that I had to manage this myself.
What could be the reason for this?
0
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
- 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
- 60 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛