🚀 go-pugleaf

"Dennis Jones" <nospam@nospam.com> wrote in message 
news:47436c88$1@newsgroups.borland.com...

> But that's just it...I didn't!

Like I said, you *or something else on the machine* had to have done it. 
"Address and port are already in use" does not occur if the IP/Port was not 
previously bound to a socket.

> Yes, I am aware of that.  That is actually the reason I mentioned
> that it was the first time I had run the app in over a day -- because
> that would have been more than enough time for the OS to close
> the socket.

Another socket on the machine is using the same IP/Port that you want to 
use.  Either your previous server instance is still active, or another 
program has created its own socket, or a local firewall is blocking the 
binding.  Those are the only possibilities for that particular error to 
occur.

> So you keep saying.  And in fact, that is exactly the reason I checked 
> netstat in the first place.  I assumed netstat would be accurate (but
> maybe it's not).

It is.

> The fact that netstat does not show the port in use is the only reason I 
> asked the question to begin with.  If netstat had listed
> the port, it would have been obvious that there was a problem
> with closing the socket and I wouldn't have bothered posting here!

Are you sure you are looking for the port that you are actually using in 
your code?  What exactly are you setting for the IP/Port of your server? 
Please show your actual code.

> So, being certain that netstat does not show the port in use, and
> being certain that the app is not already running, what would you
> suggest I do the next time this occurs?

The error is not possible under those conditions.  Bound sockets can't hide 
from netstat.  They are either bound or they are not.


Gambit