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

ratchata.limnumkam01

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.

umer.nalla

Hi @ratchata.limnumkam01

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 Developers

You 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

ratchata.limnumkam01

https://community.developers.refinitiv.com/discussion/comment/87038#Comment_87038

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?

umer.nalla

HI @ratchata.limnumkam01

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.