EMA OmmConsumer
API Version: RHEL8_64_GCC831
In EmaConfig.xml, we defined
<Consumer>
<Name value="consumer1"/>
<ChannelSet value="Channel_1, Channel_2"/>
<Logger value="Logger_1"/>
<Dictionary value="Dictionary_1"/>
<XmlTraceToStdout value="0"/>
</Consumer>
- When we construct OmmConsumer
mConsumer = new OmmConsumer(ommConsumerCfg);
If Channel_1 is not available, OmmException may be thrown
What is the suggest way to retry with Channel_2 when Channel_1 is not available during construct?
- What is the appropriate way to determine if the session is connected or disconnected from OmmConsumerEvent?
void EmaSession::onStatusMsg(const StatusMsg &statusMsg, const OmmConsumerEvent &event)
Answers
-
Thank you for reaching out to us.
With the ChannelSet configuration, if the Channel_1 is not available, EMA will try to use the Channel_2. You can check this from the API log.
loggerMsg
TimeStamp: 11:32:38.560
ClientName: ChannelCallbackClient
Severity: Warning
Text: Received ChannelDownReconnecting event on channel Channel_1
Instance Name Consumer_1_1
RsslReactor 0x00000227558EBBD0
RsslChannel 0x00000227558EBBD0
Error Id -1
Internal sysError 10057
Error Location\Jenkins\workspace\RTSDK_Core_DX1\OS\VS142-64\rcdev\source\rtsdk\Cpp-C\Eta\Impl\Reactor\rsslReactorWorker.c:2250
Error Text <D:\Jenkins\workspace\RTSDK_Core_DX1\OS\VS142-64\rcdev\source\rtsdk\Cpp-C\Eta\Impl\Transport\rsslSocketTransportImpl.c:6165> Error: 1002 ipcConnecting() client connect() failed. System errno: (10057)
loggerMsgEnd
loggerMsg
TimeStamp: 11:32:45.619
ClientName: ChannelCallbackClient
Severity: Warning
Text: Received ChannelDownReconnecting event on channel Channel_2
Instance Name Consumer_1_1
RsslReactor 0x00000227558EBBD0
RsslChannel 0x00000227558EBBD0
Error Id -1
Internal sysError 10057
Error Location\Jenkins\workspace\RTSDK_Core_DX1\OS\VS142-64\rcdev\source\rtsdk\Cpp-C\Eta\Impl\Reactor\rsslReactorWorker.c:2250
Error Text <D:\Jenkins\workspace\RTSDK_Core_DX1\OS\VS142-64\rcdev\source\rtsdk\Cpp-C\Eta\Impl\Transport\rsslSocketTransportImpl.c:6165> Error: 1002 ipcConnecting() client connect() failed. System errno: (10057)
loggerMsgEndThe exception is thrown due to the login request timeout (the LoginRequestTimeOut configuration).
Exception Type='OmmInvalidUsageException', Text='login failed (timed out after waiting 45000 milliseconds)', ErrorCode='-4052'
As far as I know, EMA is a high level API which manages connections on behalf of the application. Typically, you can check if the session is connected or disconnected from the API log.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 690 Datastream
- 1.4K DSS
- 629 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 559 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
- 24 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 279 Open PermID
- 45 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 713 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
- 121 Open DACS
- 1.1K RFA
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 95 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛