This problem happens randomly and not very often on systems in the field. I am not able to duplicate a failure in a development environment ... yet. That is why I am seeking assistance to imagine situations where a problem might be occurring.
Francois PIETTE wrote: > Would be interesting that you publish the call stack at the time when you > cann connect after the close. > > -- > [email protected] > The author of the freeware multi-tier middleware MidWare > The author of the freeware Internet Component Suite (ICS) > http://www.overbyte.be > > ----- Original Message ----- > From: "Mike Lenox" <[email protected]> > To: "ICS support mailing" <[email protected]> > Sent: Thursday, April 30, 2009 5:08 PM > Subject: Re: [twsocket] TTnCnx > > > Francois, > > Thanks you for the quick reply. I do not call Connect from the Close > event but, the events that cause data to be requested are asynchronous > and a request could occur almost immediately after a Close. So, I am > wondering of I should be concerned that my TTnCnx object is still in the > process of handling a call to Close when I issue a call to Connect. > > Another thought, could my problems be related to the fact that, when a > Windows socket is "closed" it does not close immediately but hangs > around for a while (I say this based on watching Netstat results). > > Any other thoughts on how a TTnCnx connection might stay up even though > Close has been called? > > Mike > > > > Francois Piette wrote: > >>> I have an application that uses a TTnCnx object to repetitively retrieve >>> data from a remote device. The application keeps a TTnCnx object and >>> alternately Connects and Closes. I am having an occasional problem with >>> the connection getting latched up, that is, it doesn’t seem to close >>> properly and since the receiving device only supports one session, >>> communication is stopped. >>> >>> >> >>> Is there a problem with calling Connect again too soon after a Close? Is >>> there some status I should be monitoring? >>> >>> >> Maybe the device doesn't like a reconnect too fast ? >> >> I don't know how you coded the application. If you call Connect from close >> event handler, try to pass by an intermediate custom message to let the >> component stop closing completely before doing anything else. >> -- >> [email protected] >> Author of ICS (Internet Component Suite, freeware) >> Author of MidWare (Multi-tier framework, freeware) >> http://www.overbyte.be >> >> >> ------------------------------------------------------------------------ >> >> >> No virus found in this incoming message. >> Checked by AVG - www.avg.com >> Version: 8.5.287 / Virus Database: 270.12.10/2088 - Release Date: 04/30/09 >> 06:01:00 >> >> >> > > > ------------------------------------------------------------------------ > > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 8.5.287 / Virus Database: 270.12.10/2088 - Release Date: 04/30/09 > 06:01:00 > > -- 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
