Refinitiv RTO price feed health checking

denys_vakhovych
denys_vakhovych Newcomer
in Elektron

Hi Refinitiv!
We are using Java EMA/ETA library for connecting to the Refinitiv RTO, and want to have a reliable health checking mechanism.
Currently, we made a decision to restart a client on 2 factors:
- if the stream state field in StatusMsg and RefreshMsg is not OPEN .
- if we did not receive any price updates with the RefreshMsg or UpdateMsg for more than 2 minutes.

But with this approach (second part), we have an issue with client restarting every weekend multiple times due to no updates coming on the weekends.

Can you suggest what would be the best practice to perform health checks?


Tagged:

Best Answer

  • Jirapongse
    Jirapongse ✭✭✭✭✭
    Answer ✓

    @denys_vakhovych

    Thank you for reaching out to us.

    Typically, there are three scenarios that cause the application stops receiving real-time data.

    1. The server cuts the connection. In this case, the item streams will be Open/Suspect. Then, the API will reconnect to the server and re-subscribe to all items.
    2. The server closes the login stream. In this case, the application needs to create a new OMMConsumer instance or the application needs to be restarted.
    3. The service is down. The item streams will be Open/Suspect and then will be changed to Open/Okay when the service is up

    EMA applications can get the disconnection and login closed events by registering to receive login events (ex330_Login_Streaming). EMA applications can get service events by registering to receive directory events (ex331_Directory_Streaming).

Answers

Categories