EMA API due to network reasons, some subscription RIC information is no longer pushed, how to re-subscribe
18
●0 ●0 ●5
EMA API due to network reasons, some subscription RIC information is no longer pushed, how to re-subscribe
Unfortunately, there is very little information in question from which to form any meaningful answer.
Please expand on the question
- what is the nature of 'Network reasons'?
- are you connecting to RTO or RTDS?
- Some "subscription is no longer pushed" - but do you continue to receive data for other instruments?
- For the instruments for which you don't receive data - did you receive any StatusMsg to indicate why - e.g. stream state closed?
The simplest way to resubscribe for an instrument is to call registerClient again for the instrument - but this may not help - depending on why you stopped receiving data for that instrument. There is usually a reason why a server may stop sending data/the API stops receiving updates for an instrument and until the issue is resolved - calling registerClient probably won't help.
- what is the nature of 'Network reasons'?For example, our server is in China, but the data source is in Singapore, so sometimes the network is not stable
- are you connecting to RTO or RTDS? LPC connect RTO
- Some "subscription is no longer pushed" - but do you continue to receive data for other instruments? Yes
- For the instruments for which you don't receive data - did you receive any StatusMsg to indicate why - e.g. stream state closed? NO,state:Suspect
Hello @zhangqingfeng ,
Please be informed that a reply has been verified as correct in answering the question, and has been marked as such.
Thanks,
-AHS
Hi,
Thank you for your participation in the forum.
Are any of the replies below satisfactory in resolving your query?
If yes please click the 'Accept' text next to the most appropriate reply. This will guide all community members who have a similar question.
Otherwise please post again offering further insight into your question.
Thanks,
AHS
25.3k
●87 ●12 ●25
The issue is most likely with LPC - or how it is reporting or handling RTO connectivity issues - if it provides data for some instruments and not others and definitely not sending status msg for those instruments that you are not receiving data for. Are you definitely handling Status Msg and logging them (some developers ignore the Status Msg)?
Have you contacted the LPC team - have they analysed the logs and advised why it stops updating some instruments?
As mentioned earlier - you could try calling registerClient to try and resubscribe the non-updating instruments - but if any upstream problem is not fixed, I cannot say this would work. Also, there would be the question of when do you try and resubscribe? How long do you wait before deciding an instrument is not updating + you will have lost updates during that time period?
My first step would be to ask the LPC team to explain why you stop receiving data for some instruments. If this issue occurs quite often, you could enable EMA tracing as well - as the trace may help the LPC team - but note that enabling EMA Trace can slow down the processing of the EMA application.
25.3k
●87 ●12 ●25
Also, can you advise why you are using LPC with EMA to connect to RTO?
EMA can connect directly to RTO - thereby removing one piece of 'middleware' and one less potential point of failure.
If it is because you want to run multiple consumers with a single MachineID, then you should speak to your Refinitiv Account team and ask them to allocate more MachineIDs to you - so you can avoid using LPC.
