RFA.NET Connectivity issues recovery handling
We use RFA.NET and LPC to get market price events stream. We have a wrapper application which uses RFA.NET and LPC to get market price events stream.
The application works by "Update" model which means we get connectivity status updates and market prices events via a queue.
In case we got login event with status other than OK, we are trying to reload our application (after recovery time threshold passed).
From time to time we have a connectivity issues like the below:
Login response: Data type : 141 Major version : 14 Minor version : 1 IsBlank : False HintMask : 2 IndicationMask : 0 MsgModelType : 1 MsgType : 1
RespType : Status RespTypeNum : 0 , Response status: StatusText : Force Logout from DACS. StatusTextW : StreamState : Closed DataState : Suspect StatusCode : 3 ,
Attributes: HintMask : 0 DataMask : 0 Name : NameType : 1 ServiceName : ServiceID : 0 ID : 0
When such event comes till now, we did the application reload as mentioned, but I'm wondering if this action is needed and if it can be helpful.
My questions:
1. Do you have any built in mechanism which deals with connectivity issue, that knows how to recover/retry from the problematic state?
2. What's the recommended way to deal with connectivity issues when occur? Is any action needed?
3. By the way, does RFA.NET coupled to .NET framework yet?
Thanks!
Best Answer
-
This is a closed login stream message.
message:Login response: Data type : 141 Major version : 14 Minor version : 1 IsBlank : False HintMask : 2 IndicationMask : 0 MsgModelType : 1 MsgType : 1 RespType : Status RespTypeNum : 0 , Response status: StatusText : TREP authentication token has expired. StatusTextW : StreamState : Closed DataState : Suspect StatusCode : 2 , Attributes: HintMask : 0 DataMask : 0 Name : NameType : 1 ServiceName : ServiceID : 0 ID : 0
The closed login stream also closes all opened streams and RFA will not recover the streams.
To handle this scenario, the application needs to re-open Login Stream to reconnect to the server by calling the registerClient method for the Login request, and then re-subscribe to all items.
RFA.NET doesn't support .NET Core.
1
Answers
-
Hello @aharonya
What the LPC version? Is it LPC version 1.2?
The OMM Login status response with the "StreamState : Closed, DataState : Suspect, and StatusText : Force Logout from DACS." means the login stream between the API and LPC is closed because of the "Force Logout from DACS. " reason.
When the application gets the Login status message with the Stream State Closed, the application needs to re-send the OMM login request message to the provider (LPC) manually, and then re-request items again.
I suggest you contact the LPC support team with the LPC information (LPC user, configuration file, log) and the disconnection time to verify the disconnection.
Could you please clarify the 3rd question? You can check the RFA .Net API API Compatibility Matrix from this document.
1 -
Hi @wasin.w,
Thanks for your response!
1. I was in contact with LPC team regrading this error. What I need to understand is what the way I should deal with connectivity issues happens during my rfa.net wrapper application running.
Do I need to do something to reconnect or it done automatically by the rfa.net infrastructure?
This is another error I see from time to time:
message:Login response: Data type : 141 Major version : 14 Minor version : 1 IsBlank : False HintMask : 2 IndicationMask : 0 MsgModelType : 1 MsgType : 1 RespType : Status RespTypeNum : 0 , Response status: StatusText : TREP authentication token has expired. StatusTextW : StreamState : Closed DataState : Suspect StatusCode : 2 , Attributes: HintMask : 0 DataMask : 0 Name : NameType : 1 ServiceName : ServiceID : 0 ID : 0
2. Regarding question 3, my question is if there isn't yet compatibility with .NET.Core?
0 -
@Jirapongse Thanks! What could be the reason for stream closing?0
-
The status contains the "TREP authentication token has expired" text.
It could be a problem in the LPC or the authentication service. You can contact the server team to verify the problem.
0 -
@Jirapongse One more question please: Do you have a replacement for the
RFA.NET. Something I can use in a more modern C# environment?0 -
Hello @aharonya
Please check my answer in this https://community.developers.refinitiv.com/questions/84815/how-to-implement-real-time-sdk-in-c-core.html post.
This Choosing a Refinitiv Real-time Streaming API article can help you too.
1 -
@Jirapongse Sorry for my digging... Regarding the re-registration in case of connectivity issue - does it require disposing and re-creation of the infra objects like Session, OmmConsumer, Queue, etc.?
Thanks!
0 -
From my test, I just registered a login request with the same OMMConsumer.
1
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 中文论坛