🚀 go-pugleaf

"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message 
news:474342ce@newsgroups.borland.com...
>
> "Dennis Jones" <nospam@nospam.com> wrote in message 
> news:47431d9f$1@newsgroups.borland.com...
>
>> I have an application which frequently fails to start with the message:
>>
>> "Could not bind socket. Address and port are already in use."
>
> That happens when you specify a local IP/Port to bind the socket to before 
> opening it, but the IP/Port is already in use by another socket.

Right, I am pretty sure I understand what the error means, I just don't 
understand *why* I am getting it.


>> The application had not been running for at least a day, and no
>> other server applications use the same port.
>
> So this error is happening for a server socket and not a clien socket?  Is 
> there anotehr instance of the app already running?

Yes, that is correct, it is a server socket.  But no, there are no other 
instances of the application running, which is why the I'm asking the 
question.  (the application uses a mutex to prevent multiple instances)


>> I have checked "netstat -a" for any indication that the port is in
>> use, but am never able to find anything.
>
> Why not?

If I knew the answer to that, I wouldn't be asking the question in the first 
place!!  That's the whole point..."netstat -a" does not show any application 
instances that reference the port number I am trying to open in my server. 
So if netstat does *not* show the port is in use, why would the server 
socket complain that it *is* in use?  That's the essence of my question.  I 
can find no indication whatsoever that the port is in use, yet the server 
complains.  How can that be?

- Dennis