Real-time optimize / "The connection closed with error: Connection reset by peer"

"post this question on behalf of my client"
the client has been disconnecting from Real-time-optimize a few times a day. The error message is "The connection closed with error: Connection reset by peer ", please see the logs below;
Does anyone knows what causes the issue and how to solve it?
__________________________________
Please refer to the logs below for the disconnection we experienced in the past week with timestamp. The disconnection issue is happening on a daily basis so it didn’t worked perfectly. The API was written in Scala.
021-08-23 19:01:50,924 SGT ERROR [akka.actor.SupervisorStrategy] - The connection closed with error: Connection reset by peer
2021-08-24 21:31:25,617 SGT ERROR [akka.actor.SupervisorStrategy] - The connection closed with error: Connection reset by peer
2021-08-26 05:09:29,699 SGT ERROR [akka.actor.SupervisorStrategy] - The connection closed with error: Connection reset by peer
2021-08-26 12:01:01,456 SGT ERROR [akka.actor.SupervisorStrategy] - The connection closed with error: Connection reset by peer
2021-08-26 14:03:15,459 SGT ERROR [akka.actor.SupervisorStrategy] - The connection closed with error: Connection reset by peer
2021-08-26 18:18:50,249 SGT ERROR [akka.actor.SupervisorStrategy] - The connection closed with error: Connection reset by peer
2021-08-27 18:35:45,415 SGT ERROR [akka.actor.SupervisorStrategy] - The connection closed with error: Connection reset by peer
Best Answer
-
One possible thing to look into is how the application is dealing with Ping/Pong messages. Applications can rely on the Ping message sent by RTO and respond with a Pong message to keep the connection alive. The potential issue with this is if the application contains a large watchlist of very active items, the Ping message sent by RTO may be queued up and by the time the application is ready to process it, RTO may disconnect because the application did not respond in a timely matter.
Alternatively, applications can utilize the “PingTimeout” attribute within the Login response to send the required Pong message.
0
Answers
-
From the error (Connection reset by peer), it looks like the RTO cut the connection.
It is better to contact the RTO team to verify if the RTO cut the connection.
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
- 630 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
- 86 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛