Hello RemObjects support team, We use the IpSuperTcpSuperChannel and IpSuperTcpClientChannel in our .NET WinForms application (version 9.4.109.1377). We have one client where they get the ‘SuperChannel timeout’ or ‘Actively refused’ error at least once a day. The only solution then is restarting th…

Did you try to adjust the settings?

Setting the KeepAlive setting to false results in a much slower program… Setting the registry key didn’t help. We didn’t get the permission to disable tcp protocol autotuning. We just had the SuperChannel timeout problem with another of our clients in an entire other program… We are starting to g…

As well as do I Ok. Let’s evaluate this one more time: When did this started to happen? Were there any changes in hardware or software prior to this? Is it possible to try in your environment a server and client app built using the latest v10 version (either with SuperTCP-base connections or with…

It started to happen in march of this year. When it started it was a weekly or 2-weekly problem, but since June it’s practically daily. No changes in hardware or software. Before march it worked for over more than a year. We will install the v10 version next week and release a new build for bot…

[image] Wouter_Devos1: It started to happen in march of this year. When it started it was a weekly or 2-weekly problem, but since June it’s practically daily. No changes in hardware or software. Before march it worked for over more than a year. Maybe a significant workload increase or amount …

Oh. One more thing. If/when the server side is again in FIN_WAIT state then could you also run netstate on the corresponding client host to check if there is a set of CLOSE_WAIT connections?

The only thing that happened is they are in the process of upgrading the client pc’s to Windows 10. But that’s not the case with the other customer who had the same issue today. The number of clients increased over time from 65 to approximatly 90. TLS Question: [image]

Theoretically it could be that there is an issue with RO SDK socket management that had been revealed by Win 10 TCP protocol implementation (or bug either). Anyway when this happens next time please try to gather both client and server netstat results.

I’ll do my best to gather the nestat results

Hello, An update on the issue: The problem occurs less frequently since upgrading to RemObjects 10. BUT when it occurs, they don’t get the ‘Actively refused’ or ‘SuperChannel timeout’ anymore. The application just hangs. After killing it with Task Manager and restarting they can continue working. …

RemObjects Talk

IpSuperTcp channels: SuperChannel TimeOut or Actively refused

Remoting SDK

net

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled