What are the root cause of “channel down” on Dictionary Stream?

After my service run for a while to received market price data, I've encountered "channel down" on login and dictionary stream. This cause my service to struck and doesn't receive any market price data from server. I've tried to recovery the service by register MMT_DICTIONARY to check this “channel down” and reinitialised the connection but I don’t know the reason why dictionary down cause my service struck.
Best Answer
-
Channel Down indicates that the connection has been lost between your computer and the server.
As a result, you would expect all open streams including Login, Dictionary etc to be closed off also.
There is an article that explains connection and item recovery - The Mechanics of EMA Connection and Item Recovery | Refinitiv Developers - note the section on Failover / ChannelSets.
If you are not using ChannelSets, you are strongly urged to do so - see this article for additional information Enterprise Message API (EMA) - Configuration Overview | Refinitiv DevelopersYou also need to identify the reason for the connection loss - are you connecting to an internal ADS or are you connecting to the cloud-based Refinitiv Real-Time Optimized service?
If internal ADS, then please contact your Market Data team to understand why your app lost the connection/was disconnected. They can check their ADS logs etc.
If you are connecting to RTO - then please raise a Ticket on My.Refinitiv for the 'Refinitiv Real-Time - Optimized' team - who can investigate their Logs etc
0
Answers
-
Hi @umer.nalla
Thank you for your detailed answer. I've already used ChannelSets. I'm not sure about ADS, is it so called TREP server?
0 -
Thanks for confirming. You are correct, the ADS is the consumer side component of the TREP (RTDS) system.
The ADS has logs that should identify why your application was disconnected from the ADS - your internal Market Data team should be able to access those logs.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 690 Datastream
- 1.5K DSS
- 629 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 560 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 281 Open PermID
- 46 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 724 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 95 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛