kets in 'CLOSED' state.
Even if the incoming queue isnt read entirely a call to close should
close it. Also I really can't find any documentation in netstat, or
elsewhere, about the 'CLOSED' state...
Any help would greatly be appreciated!
Kind Regards,
Ali Niknam
_
This looks like an issue we used to have at work, where a streaming
application suddenly started getting kevents for sockets that had been
already closed. While that was happening, a netstat output looked just
like yours. We never tracked it down, as we moved to other projects :(
Was that B
Hi Robert,
Sounds like there's a bug somewhere. Before we start trying to track it
[...]
So, with that introduction, we're interested in resolving:
Quite comprehensive indeed; thank you for all that information. I was
not aware that there was a decoupling between the various parts of the
Hi Eygene,
Just a quick "me too" message: I also used to see this on my 7.x
machines. This was with Apache servers in the proxy setup: one
I'm wondering: where these 32 bit, or 64 bit machines?
I had already tried to debug this situation and Mike Silbersack
helped me with patching the kerne
Hi Guys,
Another public follow-up: Ali has been sending me debugging information
privately due to the inclusion of application source code and IP
addresses. Tracing of the application suggests that there is an
application concurrency bug leading to one socket to be closed twice and
another so
