question

Upvotes
SamRT avatar image
7 ●1 ●1 ●4

Error when connecting to websocket || WebSocket onError: FLUSH_ERROR, Flushing frames to the server failed: Broken pipe (Write failed), Broken pipe (Write failed)"

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.

rrtorefinitiv-realtime-optimised
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

raksina.samasiri avatar image   raksina.samasiri

<AHS>

The machine ID that is affected was GE-A-00199952-3-7867.

They provided a different machine ID that did not have any issues (Machine ID GE-A-00199952-3-2190)

raksina.samasiri avatar image   raksina.samasiri
hi @SamRT ,

Please be informed that the machine IDs were removed from the post due to security and privacy issue. however, the moderators of this forum can still see it.

Thanks,
AHS

wasin.w avatar image   wasin.w

<AHS>

This question is from case 11682587.

zoya faberov avatar image   zoya faberov

Hello @SamRT ,

I see the case #11682587 closed for the lack of the information required to progress the investigation.

We hope that the issue discussed in this question been resolved, and you do not require help with the issue,

We would appreciate a brief update on the resolution on your side, it will allow us to make sure of that you are successfully connected to RRTO, as well as guide the next developers with same or similar questions or issues.

-AHS

0 Answers

· Write an Answer

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.