Is there a possibility of not getting a reply for a RIC and not getting reply of status closed?
I'm querying a multiple chaniend RIC and the process gets stuck after sometime. However the statusMsg.state is not closed, How to validate if the reply was sent and if the status was closed for a RIC ?
My current logic is :
post the batch request and wait for the refreshMsg.status to be true or check statusMsg.state having "CLOSED" string in it.
Problem is that is does not receive the refreshMsg nor it obtains the status as closed. Can you please advise.
Best Answer
-
For the RICs you provided, 0#1US+ and 1US1855V7, both return a refreshMsg with an Ok dataState (see below) when I request for each one individually. When you request for 0#1US+, it is a chain. EMA does not automatically expand chains and request the constituents on your behalf. You have to programmatically perform this task yourself.
If you are unfamiliar with chains and their processing, you can review Decoding Chains articles which goes into depths about how they are organized and processing recommendations.
RefreshMsg
streamId="6"
domain="MarketPrice Domain"
Solicited
RefreshComplete
ClearCache
state="Non-streaming / Ok / None / 'All is well'"
itemGroup="00 00"
permissionData="03 01 64 31 53 C0"
qos="RealTime/TickByTick"
seqNum="112"
name="0#1US+"
nameType="1"
serviceId="356"
serviceName="ELEKTRON_AD"
Payload dataType="FieldList"RefreshMsg
streamId="6"
domain="MarketPrice Domain"
Solicited
RefreshComplete
ClearCache
state="Non-streaming / Ok / None / 'All is well'"
itemGroup="00 00"
permissionData="03 01 64 31 53 C0"
qos="RealTime/TickByTick"
seqNum="768"
name="1US1855V7"
nameType="1"
serviceId="356"
serviceName="ELEKTRON_AD"
Payload dataType="FieldList"0
Answers
-
Hi @sagar.s,
Does your logic utilize the onStatusMsg() callback? If any of the items in your batch are invalid for example, you'll will not receive a refreshMsg with a status. You will receive a statusMsg indicating the issue.
0 -
It utilizes statusMsg.state().streamStateAsString().contains("CLOSED"). However, the RIC is valid.
Is there any other keywords I should be checking?
Should I reissue the RIC request if the above statusMsg is not received or if there is no status on refreshMSg?
0 -
Hi @sagar.s,
When an item is closed, your statusMsg looks like this:
StatusMsg
streamId="6"
domain="MarketPrice Domain"
state="Closed / Suspect / Not found / 'The record could not be found'"
name="JUNK.TEST"
nameType="1"
serviceId="356"
serviceName="ELEKTRON_AD"
StatusMsgEndPerhaps it could be a string comparison/case issue? You are looking specifically for "CLOSED". Can you provide us the output of what you are seeing?
0 -
Hi @sagar.s,
You should always receive something whether valid or invalid. Can you provide the RIC? Are you receiving a refreshMsg for this RIC?
0 -
I do not think it is a string comparison issue. Since the issue is intermittent. Sometimes I receive all the chaned RICs reply. But sometimes it doesn't get a reply.
However, I can check change the string comparison to be case insensitive and test as well.
0 -
For example, I have a RIC 0#1US+ . For the current run it doesn't get reply for 1US1855V7
0 -
Ok - I see in your original question you are processing the chain (got confused with the spelling "chaniend" :-). In this case, I would turn on XmlTrace to see what you are receiving. Within your EmaConfig.xml, you can enable with this:
<XmlTraceToFile value="1"/>
You will see alot of initial output for your dictionary download.
0 -
Sorry about the typo. I'll try the XML trace option. I tested the string comparison case issue. It is not failing due to that. Thanks Nick!
0 -
Hello @sagar.s
EMA Java provides XmlTraceToStdout Consumer entry parameter to specify whether EMA traces its messages in XML format to stdout. Please set the parameter to 1 to turn on tracing to stdout. For example:
<Consumer>
<Name value="Consumer_1"/>
...
<XmlTraceToStdout value="1"/>
</Consumer>Then, please attach the output so that we can know what message the application receives instead of refresh messages when the problem occurs.
0 -
Hi Pimchaya... thanks for the suggestion... I'll reach out to you with details.
0 -
Hi @sagar.s
Does the problem still occur? If so, please attach EMA trace log.
Note:The EMA trace log shown on the console can be long so please redirect your application command output to
a file as the syntax below:Java_command_line_runing_your_application
> output_file_name0 -
It seemed like a logical issue. I rewrote the logic. Its working now. Thanks for the help! This issue can be closed.
Thanks,
Sagar
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 37 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 698 Datastream
- 1.5K DSS
- 633 Eikon COM
- 5.2K Eikon Data APIs
- 14 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 6 Trading API
- 2.9K Elektron
- 1.5K EMA
- 256 ETA
- 564 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 283 Open PermID
- 47 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2.1K Refinitiv Data Platform
- 779 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 27 DACS Station
- 122 Open DACS
- 1.1K RFA
- 107 UPA
- 194 TREP Infrastructure
- 231 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 98 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛
