Same Price going to 2 different StreamId
We had an issue where the price going to one instrument was also being updated on a different RIC1 and RIC2. On the adh side, I did a dump on the ADH for the incoming messages from the route connection from the source application. After using the dbgLonMon and decoding the data from Hex to dec and dump the service to file to get the streamId, I found that the same price was being updated on 2 different streamId. A consumer was also connected directly to the Source application, and did not see the same price being sent to 2 RIC1 and RIC2. So this looks like when it hits the ADH, the price is being send to 2 different streamId on the ADH. Is this suppose to be the normal behaviour? If not is this a RTDS issue that I need to fix or the source application will the source application (using RFA 8.x) need to address this behaviour. Also when I do a re-subscription on RIC1 that was effected, it will consume the correct price, but if RIC2 is updated, RIC1 will get the RIC2's price.
Best Answer
-
Thank you for reaching out to us.
According to the problem description, it is not a normal behavior.
Each stream is unique for each RIC. For example, the update of stream#5 (RIC1) should not appear on the stream#6 (RIC2) so it could be the problem on the RFA API or the application side.
Please check the version of RFA API used by the application. If the application uses the old version, please consider upggrading it to use the latest version to avoid all known issues. You can download the RFA API from the Software Download. It is in the MDS - API product family.
If the issue still persists with the latest version of RFA, please contact the API support team directly via Contact Premium Support. However, you need to be a RDC (Refinitiv Developer Connect) named user to contact the API support team.
0
Answers
-
Thanks you for you response. Is there further documentation to explain how the streamId are first created/initialised?
0 -
If I remember correctly, RFA manges the stream IDs under the hood. The application will use the request token to send data for each item.
cmd.setMsg((OMMMsg)_encoder.getEncodedObject());
cmd.setToken(event.getRequestToken());Please refer to the RFA Developers Guide for more information.
0
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛