Request for assistance with API disconnect due to no server ping
RFA Version : rfa8.1.0.L1.linux statically linked
We connect successfully with no subscription, and about 2 hours later, we create first subscription, immediately after, we get following message.
From:RSSL_Adapter Id:20104 EventType:3 Text: [Tue Jun 9 08:01:22 2020]: (ComponentName) RSSL_Adapter: (Severity) Error: Ping has not been received by this connection "Connection_RSSL" within negotiated ping timeout. Connection will be shut down. Negotiated ping timeout is set to: 30
From:RSSL_Adapter Id:10105 EventType:3 Text: [Tue Jun 9 08:01:22 2020]: (ComponentName) RSSL_Adapter: (Severity) Error: 10105 (Default::Connection_RSSL ld6mdsads1p.ldr.jefco.com:14002)
From:RSSL_Cons_Adapter Id:6015 EventType:1 Text: [Tue Jun 9 08:01:22 2020]: (ComponentName) RSSL_Cons_Adapter: (Severity) Information: Initialization of RSSL_Cons_Adapter "Default::Connection_RSSL ld6mdsads1p.ldr.jefco.com:14002" failed, will retry in State: "Down" StatusCode: "None" StatusText: Connection down milliseconds
the threading model id "dual" and we do use EventQueues.
We need to reconnect, and we do not get same issue after that for the rest of trading day.
Any guidance and direction would be highly appreciated.
Thanks, Sanjay
Best Answer
-
Hello Sanjay @sgirdhar,
The behavior that you describe does not sound common or intuitive and most likely is not directly related to RFA API.
I would approach troubleshooting this two-fold.
1. Run another client, not custom, for test purposes, start it, login, and only send the first subscription request after 2 hours, and see if the behavior is the same. I would try testing with one of the consumer examples that came with RFA SDK, and introduce delay of 2 hrs (would do a reasonable sleep in a loop), prior to subscription or thinking perhaps rmdstestclient that comes with Infra Tools package, using it in interactive mode.
2. I would report this behavior to your local market data group/admin, people who maintain infrastructure, local TREP. Try to find out how these daily disconnects are reflected in the infrustructure log, and if nothing definite, if additional logging can be added to help better understand the reasons behind them.
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.5K 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
- 560 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
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 281 Open PermID
- 46 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 724 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 中文论坛