Regarding the cause of disconnection from Real-Time-Optimized.

yuichiro.saito · 2025-02-17T03:08:41+00:00

There was an error rendering this rich post.

Hi.

We are retrieving data from Real-Time-Optimized (hereinafter RTO). Data has been collected from 08:55:00 to 19:30:00 Japan time, but on 2025/02/13, the following message was output at 15:16:11, and we were disconnected from RTO. What was the cause of the disconnection? Also, for the 15 minutes prior to the disconnection, data was collected that was quite divergent from the actual rate. What is the cause of this? (RIC: JPY=, Field Id: 22, 25)

2 13, 2025 3:16:11 PM com.refinitiv.ema.access.ChannelCallbackClient reactorChannelEventCallback
WARN: loggerMsg
ClientName: ChannelCallbackClient
Severity: Warning
Text: Received ChannelDownReconnecting event on channel Channel_1
RsslReactor @707c8ef8
RsslChannel @66f606c3
Error Id 0
Internal sysError 0
Error Location null
Error text Tunnel Channel disconnected
loggerMsgEnd

2 13, 2025 3:16:11 PM com.refinitiv.ema.access.LoginCallbackClient rdmLoginMsgCallback
WARN: loggerMsg
ClientName: LoginCallbackClient
Severity: Warning
Text: RDMLogin stream state was changed to suspect with status message
username <not set>
usernameType <not set>

State: Open/Suspect/None - text: ""
loggerMsgEnd

2 13, 2025 3:16:11 PM com.refinitiv.ema.access.ChannelDictionary processCallback
WARN: loggerMsg
ClientName: ChannelDictionary
Severity: Warning
Text: RDMDictionary stream was closed with status message
streamId 3
Reason State: Closed, Recoverable/Suspect/None - text: "channel down."
loggerMsgEnd

2 13, 2025 3:16:11 PM com.refinitiv.ema.access.ChannelDictionary processCallback
WARN: loggerMsg
ClientName: ChannelDictionary
Severity: Warning
Text: RDMDictionary stream was closed with status message
streamId 4
Reason State: Closed, Recoverable/Suspect/None - text: "channel down."
loggerMsgEnd

Component react.asset.discussionTagsAsset had an error.

Resolver not registered: react.asset.discussionTagsAsset

Accepted answers

All comments

wasin.w

Hello @yuichiro.saito

The given API log messages do not show the reason why a disconnection occurred.

There might be a slow consumer issue as the JPY= RIC is a high update rate RIC.

Ann application should not take much time in the onRefreshMsg(), onUpdateMsg(), and onStatusMsg() callback methods. The reason is those methods need to fast to avoid a slow consumer issue that the application to slow to dispatch incoming message and leads to a disconnection issue eventually.

You can clone and copy the EMA messages to decode or process in other threads outside the callbacks with the following methods:

RefreshMsg refreshCopy = EmaFactory.createRefreshMsg(RefreshMsg original)
UpdateMsg updateCopy = EmaFactory.createUpdateMsg(UpdateMsg original)
StatusMsg StatusCopy = EmaFactory.createStatusMsg(StatusMsg original)

If you need to verify the issue on the server side, I suggest you contact the RTO Support team . You can contact the team via https://myaccount.lseg.com/en/productsupport website.

To minimize a data loss issue when a disconnection event occurs, an application can use the Warm Standby feature. You can find more detail about this feature from the following articles:

I hope this helps.

yuichiro.saito

Hello @wasin.w.

Thank you for your response. It was mentioned that "JPY= RIC is a high update rate RIC," but how many times per second can "JPY=" be updated? If the processing speed on the RTO side is too fast for our application to handle, does that mean we are acquiring data that is delayed and different from the actual data?

Jirapongse

@yuichiro.saito

It is better to contact the server team to verify the cause of disconnections.

Regarding the update rate of RTO, please refer to this discussion.

Component react.asset.createComment had an error.

Permission Problem You need the session.valid permission to do that.

EXPLORE OUR SITES