How can we be sure that a MarketPrice stream is closed?
Hi,
UPA Version: 8.0.0.L1
We have an application using UPA which creates/closes market price streams, and reuses streamIDs. The current logic for closing a stream is as follows:
- Send RsslCloseMsg, set flag so we are sent an ACK.
- Once ACK is received, add streamID to list to be reused.
We are seeing a few issues with this. If the stream is busy, we can receive some UPDATES after we receive the ACK.
Also, if we 'quickly' reuse the streamID and send an open request after we receive the ACK, we get the following message:
"Request Rejected: Cannot request new item on open stream."
Is it correct to assume that once we receive an ACK from a CloseMsg the streamId can be reused / the previous stream is correctly closed?
We have also tried using rsslIsFinalMsg to check if we have received the final message for the stream, but this always returns false for close message ACKS.
Thanks
Best Answer
-
Hello @Mike Slade,
Yes. The issue you are seeing is related to resubscribe, part of the same issue as the resubscribe failure, and was addressed in TREP 3.3.1 infrastructure.
Therefore, it's important to find out what infra you are connecting to. Your market data team/admin will know the version.
If it's below 3.3.1, you will not be able to fully rely on the ack and will have to introduce a wait after close on the app side to be fully sure it is completely closed.
0
Answers
-
Just realised this is possibly a duplicate of https://community.developers.refinitiv.com/questions/35892/when-can-i-resubscribe-after-closing-to-a-differen.html. Is someone able to confirm this?
0 -
Just realised this is possibly a duplicate of https://community.developers.refinitiv.com/questions/35892/when-can-i-resubscribe-after-closing-to-a-differen.html. Can someone confirm this?
0
Categories
- All Categories
- 6 AHS
- 39 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
- 370 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
- 60 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛