EMA:Failed to perform transport secure channel connections to hosts. Error: Couldn't add the channel
loggerMsg
ClientName: LoginCallbackClient
Severity: Error
Text: RDMLogin stream was closed with status message
username <not set>
usernameType <not set>
State: Closed/Suspect/Usage error - text: "Failed to perform transport secure channel connections to hosts. Error: Couldn't add the channel to the token session as the token reissue interval(-2319 ms) is too small."
loggerMsgEnd
three question:
one:Why does this happen?
two:How do I catch this exception error?
three:How to handle this error? (Code examples would be great)
Best Answer
-
You need to contact the LPC support team via MyRefinitiv to verify the error.
The error was sent in the login status message with the closed stream state so EMA will not recover the connection.
loggerMsg
ClientName: LoginCallbackClient
Severity: Error
Text: RDMLogin stream was closed with status message
username <not set>
usernameType <not set>
State: Closed/Suspect/Usage error - text: "Failed to perform transport secure channel connections to hosts. Error: Couldn't add the channel to the token session as the token reissue interval(-2319 ms) is too small."
loggerMsgEndHowever, the application can detect it by registering the login request to receive the login status messages in the callback, as shown in the example 333.
Then, if the application received the login status message with the closed stream state, the application can create a new consumer to connect to LPC.
0
Answers
-
@zhangqingfeng
Are you getting this error while connecting to LPC?
0 -
Yes,connecting LPC0
-
Thanks,i will test example 333,if it works and then accepts this comment0
-
Hi @Jirapongse
According to our production, we can only catch Ok and Suspect instead of Close states
0 -
For the login stream, if the stream state (statusMsg.state().streamState()) is still opened (StreamState.OPEN) but the data state (statusMsg.state().dataState()) is suspect (DataState.SUSPECT), typically, EMA will recover the connection on behalf of the application.
StatusMsg
streamId="1"
domain="Login Domain"
state="Open / Suspect / None / 'channel down'"
name="user"
nameType="1"
StatusMsgEnd0 -
Hi Jirapongse,
could you advise how to capture stream state (statusMsg.state().streamState()) is Closed ? Client want to capture it and rebuild consumer.
thanks
0 -
Statusmsg.state().streamState()or refreshmsg.state ().streamState() can be fetched to closed?
0 -
Both refresh and status messages contain stream states. You can check stream states on both refresh and status messages.
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 中文论坛