| Dart Home | PowerTCP Sockets for .NET | Custom Development | Reply | PowerTCP Sockets for .NET (Secure and Standard) Topics | Forums |
| Author | Forum: PowerTCP Sockets for .NET (Secure and Standard) Topic: When remotes do not finish SSL negotiation |
| theincrediblepeep From: Dallas, TX USA Posts: 11 Member Since: 07/07/06 |
posted January 8, 2009 5:42 PM I have an SslSockets.Server listening on my application. When I check the connection log after a few days of operation and compare it to a current netstat, I find connections that never completed SSL negotiation and still remain connected. I cannot depend on these rogue and idle sockets clearing on their own, but because SSL negotiation has not been completed, I never see them as "connected" calls at the application level in order to police them. Is there any way to tell the API to time out the SSL negotiation after, say, 5 minutes? This is on SslSockets v1.0.9. |
| theincrediblepeep From: Dallas, TX USA Posts: 11 Member Since: 07/07/06 |
posted March 18, 2009 1:21 PM Surely other people are having this issue. Uncommitted SSL connections keep building up until evenually threads and allocations are so out of control they break the app. I refuse to believe that Dart expects us to constantly restart and babysit programs that use this SSLSockets. Is there no way to police SSL negotiation before a connect event? |
| Jason Farrar (Admin) From: Oneida, NY USA Posts: 223 Member Since: 07/24/07 Extra Support Options Custom Application Development |
posted March 18, 2009 5:59 PM I've been able to replicate this issue and have recorded it as issue #5023. You can contact Jamie Powell (jamie.powell@dart.com) for details on the release of a possible fix. ------ |
| theincrediblepeep From: Dallas, TX USA Posts: 11 Member Since: 07/07/06 |
posted March 19, 2009 10:53 AM Thank you for your assistance on the matter. As a point of documentation, you may want to log that the issue is especially visible when accepting secure TCP traffic over wireless. Let me know if additional information is needed. |
| theincrediblepeep From: Dallas, TX USA Posts: 11 Member Since: 07/07/06 |
posted November 4, 2010 11:28 AM In case this information helps anyone else, upgrading to Secure Sockets v1.1.1.0 resolves this issue. As indicated in the release notes, it manages SSL negotiation and disconnects the socket in 10 seconds if secure negotiation is not complete. Great improvement. |
| Reply | PowerTCP Sockets for .NET (Secure and Standard) Topics | Forums |
This site is powered by
PowerTCP WebServer for ActiveX
|