Hi @cbhavsar

As well as raising the ticket, you should also amend your program to attempt a fresh authenticate,reconnect and login automatically when the websocket is closed off.

The examples we provide are basic ones for demo purposes only and therefore do not include the above type of behaviour - which should be added to production implementations.

Obviously, this does not mean that you won't necessarily lose any updates - but it can potentially avoid manual intervention.

Hi @cbhavsar

Please provide more details on when you see this error so we can assist.

Does it happen every time you run the example?

Are you able to get any data successfully at all?

At what point in the example run process does the error occur? e.g. before or after the GetAuthenticationInfo, before or after the ConnectAsync, before after a ReceiveMessage?

Please provide console output (remove any secure information) also.

Hi Umer-

Please find addition details as below.

Does it happen every time you run the example?

>>Nope. I come occasionally like once or twice in hours.

Are you able to get any data successfully at all?

>>Yes, we get data if do not get this exception. if we try to reconnect then it starts working fine

but we lose valuable updates in between disconnect and connect.

At what point in the example run process does the error occur? e.g. before or after the GetAuthenticationInfo, before or after the ConnectAsync, before after a ReceiveMessage?

>>before after a ReceiveMessage?

Please provide console output (remove any secure information) also.

>> I will send console output once I get error next time. I have lost it for last run,

Please see if stack trace helps in the attachments if that helps in the meantime,

Hi @cbhavsar

I am assuming you are sending Ping / Pong response in a timely manner and refreshing the tokens - which I expect is the case if problem occurs after 1-2 hrs of runtime.

Also, I can see in the stack trace:

Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host

Therefore, you should raise a Ticket with the ERT in Cloud team - providing details of times when the exceptions occurred and including the stack trace.

The team has access to the ERTiC systems and can assist you with diagnostics.

Make sure you mention that the problem also occurs with the Refintiv supplied example MarketPriceEdpGwAuthenticationExample.

Ok. I will raise ticket with support.

Thanks for the help Umer

Yes, In my application I do reconnect, send login and request items. but I wanted to check if my application is having the issue. I ran sample application and tested and I got same error in sample application as well. so I am not sure what is the reason for this error.