Subscribe to the Source Directory Information
I used the following code to register the client to the source directory domain
loginMsg.domainType(MMT_LOGIN).name("user").nameType(USER_NAME)
.attrib(ElementList().addAscii(ENAME_APP_ID, "127")
.addAscii(ENAME_POSITION, 127.0.0.1/net)
.addUInt(ENAME_ALLOW_SUSPECT_DATA, 0)
.addUInt(ENAME_SINGLE_OPEN, 1)
.addUInt(ENAME_ROLE, 1)
.addUInt(ENAME_DOWNLOAD_CON_CONFIG,1)
.complete());
directoryMsg.domainType(MMT_DIRECTORY).serviceName("DIRECT_FEED");
receiver = new OmmConsumer(OmmConsumerConfig().config(configMap));
receiver->registerClient(loginMsg, (*this), closure);
receiver->registerClient(directoryMsg, (*this), closure);
and in sample provider gave the following result.
what could be the reason for this is it a problem with the configurations I'm using.
Client Channel fd=4 is now ACTIVE
Connection is from eta3.0.2.L1.rrg|ema3.0.3.15.linux 64-bit Shared Library(Optimized) device.
Received Login Request for Username: user
Compression Stats Bytes In: 30 Uncompressed Bytes In: 30
Using 60 as pingTimeout for Channel 4
Received Source Directory Request
Compression Stats Bytes In: 20 Uncompressed Bytes In: 20
Received Dictionary Request for DictionaryName: RWFFld
Compression Stats Bytes In: 59 Uncompressed Bytes In: 29
Received Dictionary Request for DictionaryName: RWFEnum
Compression Stats Bytes In: 0 Uncompressed Bytes In: 30
channelInactive fd=4 <<Impl/ripcsrvr.c:6654> Error:1002 ripcRead() failure. Connection reset by peer
>
Closing dictionary stream id 4 with dictionary name: RWFFld
Closing dictionary stream id 5 with dictionary name: RWFEnum
Closing source directory stream id 2 with service name: DIRECT_FEED
Closing login stream id 1 with user name: user
Best Answer
-
Hi @thimalk
The "Connection reset by peer" means that the connection has been terminated by other side. This means that the EMA consumer application cut the connection. The EMA log and your EMA consumer output needs to be verified. Could you provide these logs?
0
Answers
-
Hi @thimalk
Please confirm which sample Provider you are using?
And also include the configuration you are using for the Consumer and Provider.
Thanks.
0 -
I'm using the programmatic configuration, and I have included the configurations as an attachment config.txt
for provider I'm using ETA provider in applications/Examples/Provider with default configurations
Can this configurations has any effect on this.
0 -
I have attached the ema log related to this.
please let me know if you need anymore detail
0 -
for other domains like login, dictionary and market price I can subscribed through registerclient method without issue.
Is there specific configurations for source directory domain.
0 -
The ema log looks fine. I have also tried your code. My application can receive directory response properly. What happened in your EMA application once the issue occurred? Do you have any console log?
Moreover, how does your application handle the directory response in the callback function?
0 -
I found the error, as you said problem is with the callback function.
I'm trying to access all messages as market price messages and when I access a source directory message like that all reuters thread will exit without any error.
Now I added filter for each message and handle them separately and now it working correctly
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
- 684 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
- 249 ETA
- 554 WebSocket API
- 37 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
- 643 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
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 192 TREP Infrastructure
- 228 TRKD
- 915 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 中文论坛