"Domain type does not match existing request." in EMA API C++ Sample code consummer11
We are having issues with EMA API C++ Sample code consummer113. The sample code was found to have this problem today. It used to work ok.
loggerMsg
TimeStamp: 13:42:52.398
ClientName: ChannelCallbackClient
Severity: Success
Text: Received ChannelUp event on channel Channel_3
Instance Name Consumer_3_1
Connected component version: ads3.4.2.L1.linux.tis.rrg 64-bit
loggerMsgEnd
loggerMsg
TimeStamp: 13:42:53.167
ClientName: SingleItem
Severity: Error
Text: Internal error: rsslReactorSubmitMsg() failed in SingleItem::submit( RsslRequestMsg* )
RsslChannel 0x(nil)
Error Id -29
Internal sysError 0
Error Location /r/emalib/Cpp-C/Eta/Impl/Reactor/Watchlist/wlItem.c:697
Error Text Domain type does not match existing request.
loggerMsgEnd
loggerMsg
TimeStamp: 13:42:53.167
ClientName: Consumer_3_1
Severity: Error
Text: Failed to open or modify item request. Reason: RSSL_RET_INVALID_DATA. Error text: Domain type does not match existing request.
loggerMsgEnd
Exception Type='OmmInvalidUsageException', Text='Failed to open or modify item request. Reason: RSSL_RET_INVALID_DATA. Error text: Domain type does not match existing request.', ErrorCode='-29'
Best regards,
Yongguang
Best Answer
-
From my checking, I assume that you are using EMA 3.5.0.L1 in Real-Time SDK C/CPP 1.5.0.L1.
It looks like to be a bug fixed in EMA C++ 3.5.1.L1 in RTSDK C++/C Release 1.5.1.L1.
- [ESDK-4086] - EMA must check both DictionaryUsed and DictionaryProvided to download dictionary from network
The workaround for EMA 3.5.0.L1 is loading the dictionary from the local files by using Dictionary_2 in Consumer_3.
<Consumer>
<Name value="Consumer_3"/>
<!-- ChannelSet specifies an ordered list of Channels to which OmmConsumer will attempt to -->
<!-- connect, one at a time, if the previous one fails to connect -->
<ChannelSet value="Channel_3"/>
<Logger value="Logger_1"/>
<Dictionary value="Dictionary_2"/>
<XmlTraceToStdout value="0"/>
</Consumer><Dictionary>
<Name value="Dictionary_2"/>
<DictionaryType value="DictionaryType::FileDictionary"/>
<!-- dictionary names are optional: defaulted to RDMFieldDictionary and enumtype.def -->
<RdmFieldDictionaryFileName value="./RDMFieldDictionary"/>
<EnumTypeDefFileName value="./enumtype.def"/>
</Dictionary>Then, copy the RDMFieldDictionary and enumtype.def files from the Cpp-C\etc to the working directory of the application.
Otherwise, you can upgrade to the latest version of the Refinitiv Real-Time SDK.
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
- 685 Datastream
- 1.4K DSS
- 615 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 252 ETA
- 556 WebSocket API
- 38 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 652 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
- 104 UPA
- 193 TREP Infrastructure
- 228 TRKD
- 917 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛