C# RFA Consumer Application stops getting events
We have an application where we occasionally are seeing stale/incorrect data for a handful of RICs out of the 1000s we are subscribed to. After some digging it appears like the data is stale because the ProcessEvent method of the ThomsonReuters.RFA.Common.Client we passed in to the OMMConsumer.RegisterClient is no longer being called. We think we are logging/handling all the events that would be notifying us of any issues/errors, but we are not finding anything in any logs (RFA, application, ADS, ADH, etc). If we redo the whole RegisterClient process, we again start to receive events. If we use the ADS example application to watch the same RIC, in our app no updates, in the example apps we see updates.
We do not think we were seeing this issue prior to retiring an old SSL application that subscribed to the same set of RICs. That application also subscribed to everything fresh each morning. Our environment also has a Conflated+RealTime feed and a Conflated+Delayed feed in addition to the normal RealTime feed (IDN_RDF). From what we can tell we are not having this issue on the RealTime feed, only on the other 2.
Any help/pointers would be greatly appreciated.
Client Environment:
RFA.Net: 8.1.01
Windows: Server2008 R2
VisualStudio: 2017
.NET Framework: 4.6.1
TREP Environment:
ADH: adh2.6.3.L1.linux.tis.rrg
ADS: ads2.6.1.L1.linux.tis.rrg
DACS: dacs7.1.0.L1.infra_6X.64.rrg
RedHat: RHEL Server 6.4
Best Answer
-
We got trace files from the client and found that TREP has sent CLOSED status message with "Record dropped from network" text. The content team confirmed that BN.H was delisted and then relisted by NYSE.
In this case, the application needs to re-subscribe to BN.H in order to get the data.
0
Answers
-
-Do you receive response message type Refresh or Status for the RICs you mentioned?
-Can you test the same set of RIC using StarterConsumer example? and Is this possible to turn on RSSL trace in your application? You can add RFA configuration provided in this post to turn on the log. It could help confirm if the RFA still receieving data at the time your application not get the events.
If problem persists please open a new support ticket to API support team to investigate the issue further.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
- 370 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 中文论坛