- Original Message -
From: "Mike Lenox"
To: "ICS support mailing"
Sent: Thursday, April 30, 2009 9:06 PM
Subject: Re: [twsocket] TTnCnx
This problem happens randomly and not very often on systems in the
field. I am not able to duplicate a failure in a development
t;
> - Original Message -
> From: "Mike Lenox"
> To: "ICS support mailing"
> 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
-
From: "Mike Lenox"
To: "ICS support mailing"
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
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
pr
>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 an
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
