directory retrieval failed
Trying to get index pricing from production server (ads1.trep-s.prod-inx.cityindex.co.uk:14002) fails with below "directory retrieval failed" error. This error occurs from when running in our kubernetes AKS cluster. Connecting to pre-production servers works fine. Also, connecting to prod server from development machine running on windows work fine.
emaLog_1.log:
ClientName: ChannelCallbackClient
Severity: Info Text: Received ChannelUp event on channel Channel_Index
Instance Name Consumer_Index_2
Component Version ads3.5.0.L1.linux.rrg 64-bit
loggerMsgEnd
WARN|: loggerMsg
ClientName: DirectoryCallbackClient
Severity: Warning Text: Received RDMDirectory status message without the state
loggerMsgEnd
WARN|: loggerMsg
ClientName: ChannelCallbackClient
Severity: Warning Text: Received ChannelDownReconnecting event on channel Channel_Index
Instance Name Consumer_Index_2
Reactor 60811181
Channel 10429724
Error Id SUCCESS
Internal sysError 0
Error Location Reactor.ProcessReactorEventImpl
Error text Ping error for channel: Lost contact with connection... Client channel has connection attempts left
loggerMsgEnd
WARN|: loggerMsg
ClientName: LoginCallbackClient
Severity: Warning Text: RDMLogin stream state was changed to suspect with status message
username <not set>
usernameType <not set>
State: Open/Suspect/None - text: ""
loggerMsgEnd
ERROR|: loggerMsg
ClientName: Consumer_Index_2
Severity: Error Text: directory retrieval failed (timed out after waiting 60000 milliseconds) for ads1.trep-s.prod-inx.cityindex.co.uk:14002)
loggerMsgEnd
Best Answer
-
I checked the PCAP file and found a lot of TCP Retransmission messages from 36900 -> 14002. That message could be the source directory request message. This indicates that the source directory request message couldn't be sent to the server. This could be a network issue.
0
Answers
-
I tried setting the value to 0, now the application waits forever0
-
You may need to enable XML trace on the consumer to verify the incomming and outgoing messages. For example:
<Consumer>
<Name value="Consumer_1"/>
<Channel value="Channel_1"/>
<Dictionary value="Dictionary_1"/>
<XmlTraceToStdout value="1"/>
</Consumer>0 -
I have network capture pcap file too, if you need0
-
index-trace-full.txt full trace
0 -
-
I checked the full trace file and found the following behavior.
The API received the source directory refresh message at 18:20:33. I am not sure why it sent a new login request at 18:20:34. After that, it was unable to retrieve any source directory refresh messages from the server.Please check the version of EMA used by the application. If the application uses the old version, please try to upgrade the application to use the latest version. You can download the APIs from the Software Downloads. The APIs are in the MDS - API product family.
Yes, please share the PCAP file. I will check which side reset the connections.
However, normally Developer Community Forum is for how-to/general questions but your question seems to be more complex and requires investigation e.g. review source code, configuration, try to reproduce the problem etc. I recommend you raise a query through the premium support service. If you are a named user of that service you should see a link "Contact Premium Support" when you are logged into the developer portal.
0 -
0003-pcap.zip attached pcap file. We are using LSEG.Ema.Core (3.2.0.1). That is the latest dll that is available on nuget. Will try the premium support. Thanks for the help so far.
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
- 616 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 中文论坛
