tls/http socket issue
- From: paul_beattie@xxxxxxxxxxx
- Date: 28 Nov 2006 14:02:38 -0800
Hi,
I'm currently encountering some odd behaviour with tls. Basically I am
polling a server via https. I start a small group of timers which
carry out asynchronous calls to the https server. Each of my 10 timers
polls the server every 10 seconds and have a timeout of 5 seconds.
What I notice is that on some occasions the third party https server
will timeout/disconnect. When this occurs my callback via the geturl
command returns and the http package indicates a timeout. I then see
that http has closed the socket and shut down the fileevents. However
my CPU usage jumps to 90+%. When I strace the program I see that the
socket tcl has just closed is still trying to read and is getting
resource unavailable errors. The socket never issues a close call in
the strace after this point. A result the reading continues and the
CPU usage hammers away to 99%.
I do have a vwait in my main application so as a matter of course I
wrote a new version of http which does not require vwaits at all. It
uses purely tls, sockets and callbacks. With this I still observe the
same behaviour.
Does anyone know of any issues with tls when the server does not close
down the socket cleanly? I have tried simulating this problem with a
simple cgi script but to no avail.
.
- Prev by Date: Re: tcl-trace
- Next by Date: Re: mixing xml, dom and tdom
- Previous by thread: mixing xml, dom and tdom
- Next by thread: transparency
- Index(es):
Relevant Pages
|
