At what frequency, Dispatch method dispatches the messages on the Reactor Channel?
The below code snippet is from the Consumer Value Add example. On Executing this, looks like the reactor dispatches the messages after every 10 seconds. But doesn't look like it is configured in the example code. I wanted to ask if this Reactor's implicit behavior to dispatch the messages after every 10 seconds or this can be controlled by the API user?
// dispatch until no more messages
while ((ret = reactorChnl.dispatch(dispatchOptions, errorInfo)) > 0) {}
if (ret == ReactorReturnCodes.FAILURE)
{
if (reactorChnl.state() != ReactorChannel.State.CLOSED &&
reactorChnl.state() != ReactorChannel.State.DOWN_RECONNECTING)
{
System.out.println("ReactorChannel dispatch failed: " + ret + "(" + errorInfo.error().text() + ")");
uninitialize();
System.exit(ReactorReturnCodes.FAILURE);
}
}
Best Answer
-
In the Consumer Value Add example, reactorChnl.dispatch()
will be called after selector.select() returns and there is data available to
be read in the reactor channel.private void run()
{
int selectRetVal, selectTime = 1000;
while (true)
{
Set<SelectionKey> keySet = null;
try
{
selectRetVal = selector.select(selectTime);
if (selectRetVal > 0)
{
keySet = selector.selectedKeys();
}
}
…
}Then, reactorChnl.dispatch() will be called until there is no more messages to process.
while ((ret = reactorChnl.dispatch(dispatchOptions, errorInfo)) > 0) {}
The return value of ReactorChannel.dispatch() can be:
- A positive value if dispatching succeeded and
there are more messages to process
- ReactorReturnCodes.SUCCESS if dispatching
succeeded and there are no more messages to process
- ReactorReturnCodes.FAILURE, if dispatching
failed (refer to errorInfo for additional information)
From this information, the Consumer Value Add example will
dispatch the messages when there are messages available to process. It will not
dispatch the messages after every 10 seconds except the code was modified or
the data comes every 10 seconds.0 - A positive value if dispatching succeeded and
Answers
-
Reactor dispatch is controlled by dispatchOptions, which is defined by maxMessages to process, which by default is 100. Therefore, usually dispatch fully dispatches the messages available on the descriptor, and if more is expected, it can be set higher.
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 中文论坛