Error when connecting to websocket || WebSocket onError: FLUSH_ERROR, Flushing frames to the server
Hi Team,
We have an inquiry received from TOTVS S.A.
Initial inquiry: "we had an incident again, today 9/26/2022, where we received the following error message:
"2022-09-26T15:36:42.934Z","""sf-ldc-core-prd""","2022-09-26 15:36:41.526 ERROR 1 --- [ WritingThread] c.t.s.l.w.s.WebSocketClientService : WebSocket onError: FLUSH_ERROR, Flushing frames to the server failed: Broken pipe (Write failed), Broken pipe (Write failed)"
"2022-09-26T15:36:42.934Z","""sf-ldc-core-prd""","2022-09-26 15:36:41.526 ERROR 1 --- [ WritingThread] c.t.s.l.w.s.WebSocketClientService : WebSocket onSendError: FLUSH_ERROR, Flushing frames to the server failed: Broken pipe (Write failed), Broken pipe (Write failed)"
"2022-09-26T15:36:42.934Z","""sf-ldc-core-prd""","2022-09-26 15:36:41.526 ERROR 1 --- [ WritingThread] c.t.s.l.w.s.WebSocketClientService : WebSocket onError: FLUSH_ERROR, Flushing frames to the server failed: Broken pipe (Write failed), Broken pipe (Write failed)"
"2022-09-26T15:36:42.934Z","""sf-ldc-core-prd""","2022-09-26 15:36:41.526 ERROR 1 --- [ WritingThread] c.t.s.l.w.s.WebSocketClientService : WebSocket onSendError: FLUSH_ERROR, Flushing frames to the server failed: Broken pipe (Write failed), Broken pipe (Write failed)"
After that, we didn't receive any further updates from Refinitiv until we restarted the entire communication process.
It's the same issue reported in Refinitiv Case 11584065 to which we got the return that we didn't respond to the PING request, however in this case we did, as seen below:
"2022-09-26T15:36:06.625Z","""sf-ldc-core-prd""","2022-09-26 15:36:06.346 INFO 1 --- [ ReadingThread] c.t.s.l.w.s.WebSocketClientService : RECEIVED CONNECT: [{""Type"":""Ping""}] /192.168.26.138:49450"
"2022-09-26T15:36:06.625Z","""sf-ldc-core-prd""","2022-09-26 15:36:06.346 WARN 1 --- [ ReadingThread] c.t.s.l.w.s.WebSocketClientService : SENT: {""Type"":""Pong""}"
"
The machine ID that is affected was GE-A-xxxxx.
They provided a different machine ID that did not have any issues (Machine ID GE-A-xxxxx)
Upon collaborating with our enterprise specialist, We can confirm that the issue was not from the Refinitiv side, hence we are asking for your assistance in resolving this issue.
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛