I could be wrong and haven't time to scan your code. But there is an error condition that will arise if all the client ports are used (and to be tautologous) no more are available; 64k ports is a lot so hardly happens. It would most likely happen in the conditions you describe - none for period of time sudden increase in errors (depending on resilience of code). If I'm reading your usage of ports correctly - 40 connections a second - and the necessary wait time after port close - you possibly hitting it.
Stephen Dickason Senior Developer - Managed Services Email: sdicka...@elcb.co.za ELCB Information Services (Pty) Ltd Customer Service Email e...@elcb.co.za * www.elcb.co.za E A S T L O N D O N Tel: +27(43) 704 0700 Fax: +27(43) 704 0701 J O H A N N E S B U R G Tel: +27(11) 879 6179 Fax: +27(11) 454 0384 P O R T E L I Z A B E T H Tel: +27(41) 373 0529 Fax: +27(86) 650 0135 Disclaimer -----Original Message----- From: TWSocket [mailto:twsocket-boun...@lists.elists.org] On Behalf Of RTT Sent: 12 August 2014 07:43 PM To: ICS support mailing Subject: Re: [twsocket] Handle Leak On 12-08-2014 16:33, Doug Billi wrote: > There are no memory leaks, and no other handle leaks, other than > security-context tokens. Testing here and I'm not seeing any token type handle listed in the process explorer list of open handles for the server or client application. The total number of handles is also stable for client and server. Using your suggested 40 connections per second, and also XE2 -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be