Is OmmConsumer::unregister a synchronous call?
It looks like call to OmmConsumer::unregister is synchronous. We are moving from RFA where equivalent call to rfa::sessionLayer::MarketDataSubscriber::unsubscribe was asynchronous. Is OmmConsumer::unregister a synchronous call? If yes, is there an asynchronous call for unsubscribe? Thanks.
Best Answer
-
Hi @nm
I have received confirmation that this is by design that only the dispatching thread can
submit message within the callback methods as the dispatching thread acquires
the lock when calling the rsslReactorDispatch method.The lock is needed to streamline the locking flow
between the EMA and the Reactor layers as the Reactor has its own locking as
well.RFA works because it does not use the Reactor and it
uses its own message queue to dispatch events from RFA.So, in answer to your other question there is no 'asynchronous call' - i.e. none that does not use the lock for unsubscribing individual streams.
0
Answers
-
Hi @nm,
Can you expand on what behaviour of RFA MarketDataSubscriber you are trying to recreate with EMA or what EMA behavior suggests synchronous behaviour?
When you call OmmConsumer::unregister for a particular items handle, it relinquishes interest in an open item stream of that item. EMA will unsubscribe that item from the server.
0 -
It seems synchronous because if a call back like onUpdateMsg is in progress and we call unregister from another thread for that item, the unregister is not going to return until the the onUpdateMsg is done. The unregister is waiting for a lock inside EMA
The lock is hold by the callback https://github.com/Refinitiv/Elektron-SDK/blob/master/Cpp-C/Ema/Src/Access/Impl/OmmBaseImpl.cpp#L1556-L1557
The code we are converting from RFA to EMA uses a lock in the onUpdateMsg. The same lock is hold by the thread that is calling the unregister method. This is getting deadlocked in EMA but does not deadlock in RFA. So in RFA we can call unregister even though a callback is in progress (waiting for a lock which is currently hold by the thread calling unregister).
0
Categories
- All Categories
- 6 AHS
- 39 Alpha
- 162 App Studio
- 4 Block Chain
- 5 Bot Platform
- 17 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 中文论坛