I am using the Shen Zhen Real time feed context id = 5940 and around 1pm everyday, I saw the message: 13:00:10.958 INFO [Refinitiv] Processing RsslRDMDirectoryMsg, 'RDM_DR_MT_UPDATE' received for channel, '{streamState: 'Unspecified', dataState: 'Suspect', code: 'None', text: ''} with services, [] and around that time 13:00:10, I found that there are missing quotes for many symbols, could you advice, what the message mean, and does it related to the missing data?
25.1k
●57 ●17 ●14
Hello @chunyung.lam
Thank you contacting us. Please see the answer below.
- streamState: 'Unspecified': streamState is unspecified. Typically used as a structure initialization value and is not intended to be encoded or decoded.
- dataState: 'Suspect':dataState is SUSPECT (also known as a stale-data state). A suspect data state means some or all of the data on a stream is out-of-date (or that it cannot be confirmed as current, e.g., the service is down).
The entire Update message's status indicates that the data is currently not available, but the API does not log the reason for it (code: 'None', text: '').
Did you encounter any disconnection or service down? Do you have more log messages when the problem occurred? If so, please give us more logs with the following information:
- The ETA version
- Is it ETA C or ETA Java or C#?
- OS and compiler detail
- Can you replicate the issue on demand?
Additionally, you can submit a support ticket to the dedicate Real-Time APIs support team (RDC) if you are the RDC named user. If you are the RDC named user, you can open the RTSDK Java or RTSDK C/C++ or RTSDK C# pages and click the "Contact premium support" button.
25.1k
●57 ●17 ●14
Hello @chunyung.lam
Based on the Refinitiv Domain Model Guide document (ETA Java, ETA C), the Source Directory Update message does not contain the State information.
However, your log message shows "Processing RsslRDMDirectoryMsg, 'RDM_DR_MT_UPDATE' received for channel, '{ streamState: 'Unspecified', dataState: 'Suspect', code: 'None', text: ''}" which is not expected for the Update message.
Can you give us the full log messages when the problem occurred? Does the issue still persist in your environment?
