Discover Refinitiv
MyRefinitiv Refinitiv Perspectives Careers
Created with Sketch.
All APIs Questions & Answers  Register |  Login
Ask a question
  • Questions
  • Tags
  • Badges
  • Unanswered
Search:
  • Home /
  • Elektron /
  • EMA /
avatar image
Question by f.heuschen · May 15, 2020 at 06:04 AM · javaloginelektron sdk - javaert cloudreissue

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

People who like this

0 Show 0
Comment
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

3 Replies

  • Sort: 
avatar image
REFINITIV
Best Answer
Answer by Pimchaya.Wongrukun · May 15, 2020 at 08:03 AM

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.

Comment

People who like this

0 Show 0 · Share
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

avatar image
REFINITIV
Answer by Pimchaya.Wongrukun · May 15, 2020 at 06:49 AM

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.



loginreissue.jpg (182.0 KiB)
Comment

People who like this

0 Show 0 · Share
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

avatar image
Answer by f.heuschen · May 15, 2020 at 07:02 AM

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 1

State: Closed/Suspect/Timeout - text: "TREP authentication token has expired."
loggerMsgEnd

Which led me to believe that I had to manage this myself.

What could be the reason for this?

Comment

People who like this

0 Show 0 · Share
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Watch this question

Add to watch list
Add to your watch list to receive emailed updates for this question. Too many emails? Change your settings >
10 People are following this question.

Related Questions

"Handshake failed with far end." error

How to use account to view data using the EMA java library?

How to get FID before creating view and ommit duplicate response

OmmConsumer and DACS onbehalf

OmmConsumer.registerClient hanging after too many tickers

  • Feedback
  • Copyright
  • Cookie Policy
  • Privacy Statement
  • Terms of Use
  • Careers
  • Anonymous
  • Sign in
  • Create
  • Ask a question
  • Spaces
  • Alpha
  • App Studio
  • Block Chain
  • Bot Platform
  • Calais
  • Connected Risk APIs
  • DSS
  • Data Fusion
  • Data Model Discovery
  • Datastream
  • Eikon COM
  • Eikon Data APIs
  • Elektron
    • EMA
    • ETA
    • WebSocket API
  • Legal One
  • Messenger Bot
  • Messenger Side by Side
  • ONESOURCE
    • Indirect Tax
  • Open PermID
    • Entity Search
  • Org ID
  • PAM
    • PAM - Logging
  • ProView
  • ProView Internal
  • Product Insight
  • Project Tracking
  • Refinitiv Data Platform
    • Refinitiv Data Platform Libraries
  • Rose's Space
  • Screening
    • Qual-ID API
    • Screening Deployed
    • Screening Online
    • World-Check One
    • World-Check One Zero Footprint
  • Side by Side Integration API
  • TR Knowledge Graph
  • TREP APIs
    • CAT
    • DACS Station
    • Open DACS
    • RFA
    • UPA
  • TREP Infrastructure
  • TRIT
  • TRKD
  • TRTH
  • Thomson One Smart
  • Transactions
    • REDI API
  • Velocity Analytics
  • Wealth Management Web Services
  • World-Check Data File
  • Explore
  • Tags
  • Questions
  • Badges