Problems overnight connecting to RDP with RTSDK

We run an application that stays up 24/7 connected to RDP. The app is written in C++ using ETA.
Roughly once a week we will be disconnected by RDP and then be unable to reconnect until we restart our application. We think perhaps something within the OpenSSL library is not being cleaned up when we call rsslCloseChannel after the disconnection and is subsequently preventing rsslConnect from returning a channel.
We would be grateful for any help with this issue.
ETA details are as follows : version=eta3.7.2.L1 internal=eta3.7.2.0 date= Mon Dec 11 16:26:10 CST 2023
Here is an excerpt from the log file.
2024-03-15T00:51:38.651Z : INFO: subsession: Attempting connection to us-east-1-aws-3-med.optimized-pricing-api.refinitiv.net:14002
2024-03-15T00:51:38.695Z : WARN: subsession: Unable to connect [-1 RSSL_RET_FAILURE,115] <ripcsslutils.c:1384> Error: 2000 ripcSSLSetupCTXClient() failed to create new context (errno 115)OpenSSL Error string: error:140A90F1:lib(20):func(169):reason(241):ssl_lib.c:1975:
2024-03-15T00:51:38.695Z : WARN: subsession: No RSSL Hosts accepted the connection request
Best Answer
-
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
Answers
-
Thank you for reaching out to us.
As far as I know, ETA supports Real-Time Optimized (Consuming Data from the Cloud) through the RsslReactor in the ETA Value Added package. Please check the VAConsumer example in the package.
Moreover, RsslReactor can reconnect to the server when it can detect a disconnection so the application that uses RsslReactor doesn't need to close and recreate a new connection.
You have mentioned the rsslCloseChannel and rsslConnect functions in the question.
Have you used ETA to consume real-time data from Real-Time Optimized without using the RsslReactor in the ETA Value Added package?
0 -
Hi
We've never used RsslReactor in the past and have no plans to rewrite our application to use it.
Currently our application connects and runs fine, consuming data from the cloud.
It's only when our socket connection is closed by the remote end and we attempt to reconnect that we end up with this problem.
0
Categories
- All Categories
- 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
- 613 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
- 248 ETA
- 552 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
- 629 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
- 191 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 84 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛