Channel Callback Client recieved ChannelDownReconnecting Message

goodsgjung

Hello

I saw the error message like below a few hours ago.

After Nasdaq market opened, the message occured.

What is ChannelDownReconnecting?

loggerMsg
    ClientName: ChannelCallbackClient
    Severity: Warning
    Text:    Received ChannelDownReconnecting event on channel DATA_CHANNEL_1
        RsslReactor =====
        RsslChannel =====
        Error Id 0
        Internal sysError 0
        Error Location null
        Error text Connection reset
loggerMsgEnd

umer.nalla

Hi @goodsgjung

Do you have a large watchlist of instruments and/or are you performing considerable processing in the main onRefesh or onUpdate callbacks? If so, you could be starving the API thread (that calls the onRefresh and onUpdate callbacks) - which could mean the API cannot read all the data from the server in a timely manner and the server disconnects you.

The above may not be the case - but I mention this because it is a possibility.

A few posts related to 'slow consumer'

EMAJ version 1.1.1.E2 keeps hitting disconnection intermittently - Forum | Refinitiv Developer Community

How can I Avoid making database call in onUpdateMsg but need result to be stored in database.Can I have an example? - Forum | Refinitiv Developer Community

RTO disconnection happen in case of many RICs to be subscribed - Forum | Refinitiv Developer Community

Are you connecting to an internal ADS server or using our RTO cloud-based service?

If internal ADS, speak to your internal MarketData team who can check the logs for any disconnects and the reason.

IF RTO, then please raise a ticket at My.Refinitiv for the Real-Time Optimised with details of your machineID and disconnect times - they may be able to check their logs also.

zoya faberov

Hello @goodsgjung ,

This likely means that channel was down and EMA API was working to recover it.

You may wish to review the discussion of "Single Open" concept in EMA RDM Guide. By default, an EMA consumer is utilizing "Single Open" and upon connection loss, EMA API attempts to recover the channel without action required from app developer. Once the channel is re-established, EMA attempts to re-subscribe any existent item streams. It is possible to modify this behavior, via attributes passed, please find the details in RDM guide.