State: Closed/Suspect/Timeout - text: "Authentication token has expired."
Our application is connecting successfully, but the connection drops after a little while. It does so systematically when restarted.
The same code works fine for other instances using other machine IDs. I have verified that only this instance use the machineID and I was confirmed that it is dedicated.
Is there a configuration that would disable or interfere with the token refresh?
Here is the output in the log:
2023-02-23 06:18:03,692 ERROR [pool-5-thread-1] | com.refinitiv.ema.access.OmmConsumerImpl | | loggerMsg
ClientName: LoginCallbackClient
Severity: Error
Text: RDMLogin stream was closed with status message
username **********************************************************
usernameType 1
State: Closed/Suspect/Timeout - text: "Authentication token has expired."
loggerMsgEnd
2023-02-23 06:18:03,692 WARN [pool-5-thread-1] | com.zerobase.reuters.MonitorConsumerClient | | received status message on monitor: StatusMsg
streamId="1"
domain="Login Domain"
state="Closed / Suspect / Timeout / 'Authentication token has expired.'"
name="**********************************************************"
nameType="1"
StatusMsgEnd
Best Answer
-
Hi @andre.malenfant,
Which version and language of SDK are you using?
There are couple of things you could try/verify:
- Have you enabled the session management for this instance? It might be specified in the EMA config file or in your code.
- Do other machine ID's successfully work on this instance of the code?
- Do you still have this issue when using this machine ID with example code provided with the SDK?
- You can also enable the XML log trace from the SDK to see whats happening on the streaming connection.
Since the token access/refresh endpoint is different from the streaming endpoint, is it possible that your firewall or other network component interfere with it. You can also play around with the token reissue ratio configuration paramete and reduce it to 0.5, see if that makes a difference.
0
Answers
-
- Can you direct me to the session management configuration documentation?
-The same code works for other machine IDs
-I cannot test examples on this environment (prod)
-I have the trace enabled, maybe not all, will check that.
0 -
Check the EMA Config guide. It is in the docs folder of the SDK. Here is the Java version of this guide - https://github.com/Refinitiv/Real-Time-SDK/tree/master/Java/Ema/Docs
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 中文论坛