handleErrorPricemarketKeyRefinitiv for Real Time Optimized

changyao.yeo

We have encountered an issue today and it shuts down the feed. The dev has extracted the log from the feed connector and below are the error message:

2022-06-10 08:13:40.321 | real-time-price | [pool-1295-thread-1] | WARN | c.r.ema.access.OmmConsumerImpl.reactorChannelEventCallback (477) | loggerMsg
2022-06-10 08:13:40.321 | real-time-price | [pool-1295-thread-1] | WARN | c.r.ema.access.OmmConsumerImpl.rdmLoginMsgCallback(295) | loggerMsg
2022-06-10 08:13:40.321 | real-time-price | [pool-1295-thread-1] | WARN | c.r.ema.access.OmmConsumerImpl.processCallback(1170) | loggerMsg
2022-06-10 08:13:40.321 | real-time-price | [pool-1295-thread-1] | WARN | c.r.ema.access.OmmConsumerImpl.processCallback(1170) | loggerMsg
2022-06-10 08:13:40.321 | real-time-price | [pool-1295-thread-1] | INFO | c.a.p.r.m.i.RefinitivHandlePriceServiceImpl.handleErrorPrice(223) |handleErrorPricemarketKey=1AE2W3470R2,msgMap={state=Open / Suspect / None / 'channel down.'}
2022-06-10 08:13:40.322 | real-time-price | [pool-1295-thread-1] | INFO | c.a.p.r.m.i.RefinitivHandlePriceServiceImpl.handleErrorPrice(254) | hdel-marketKey=1AE2W3470R2
2022-06-10 08:13:40.381 | real-time-price | [pool-1295-thread-1] | INFO | c.a.p.r.m.i.RefinitivHandlePriceServiceImpl.handleErrorPrice(223) | handleErrorPricemarketKey=1AE2W3490R2,msgMap={state=Open / Suspect / None / 'channel down.'}
2022-06-10 08:13:40.382 | real-time-price | [pool-1295-thread-1] | INFO | c.a.p.r.m.i.RefinitivHandlePriceServiceImpl.handleErrorPrice(254) | hdel-marketKey=1AE2W3490R2
2022-06-10 08:13:40.442 | real-time-price | [pool-1295-thread-1] | INFO | c.a.p.r.m.i.RefinitivHandlePriceServiceImpl.handleErrorPrice(223) | handleErrorPricemarketKey=1AE2W3500R2,msgMap={state=Open / Suspect / None / 'channel down.'}

umer.nalla

Hi @changyao.yeo

The log file above is application-level logging and is reporting some status message indicating that the connection to RTO has been lost.

There is nothing to indicate why the connection may have been lost.

You can create a ticket with the Refinitiv Real-time Optimized team to try and ascertain why the connection was lost.

The client can also amend their code to monitor the connection status - by registering for the Login stream as described in the following posts:

How can I capture the ERROR message reactorChannelEventCallback - Forum | Refinitiv Developer Community

If the StreamState of the Login Stream changes to Closed, then the application can try reconnecting to RTO. This should be done in a controlled manner e.g. try reconnecting a few times with a controlled delay between each attempt and then perhaps stop trying to connect once several attempts fail - do not repeatedly try to connect in quick succession if the connection attempts keep failing.