Re: question related to sockets
- From: "Abubakar" <emailallrise@xxxxxxxxx>
- Date: Thu, 2 Nov 2006 14:59:02 +0500
Hi,
thanks for the reply. I think the problem was related to Dr.Watson exe that
somehow was hooking the crashed app. The netstat command showed the process
that ownd the ports but it was not there in the taskbar. If I terminate the
drwatson app from taskmanager everything worked fine and i could listen on
the ports upon restarting my app..
regards,
-ab.
"Steve Alpert" <sra@xxxxxxxxxxxxxxxxx> wrote in message
news:eAVvYdE$GHA.1200@xxxxxxxxxxxxxxxxxxxxxxx
This isn't the right NG for this question. Try the networks NG.
The short answer is that the OS doesn't release a socket for up to 4 mins
and hence your reconnect would fail (unless you set a socket option to
share).
/steveA
Abubakar wrote:
Hi,
I'm working on a sockets app (using all those connect, socket, recv, send
stuff). There is one problem on just one of many pcs i deal with. This
pc, sometimes my app crashes on it, which is pretty usual cuz of
application bugs and I fix them of course. But the problem is that the
ports r left open when the app crashes. I see the list from entering the
*netstat -a -o* command at the command prompt. Its shows that the ports r
still in the listening state. The *-o* switch for this netstat command
shows the process that owns these ports but clearly that process died a
long time back and has no signs in the task manager of windows xp either.
Can any one tell me what can I do to resolve this? Logging off from the
pc and signing in again disappears the port from the netstat command
listing but the app is still unable to listen on these ports. If I
restart the computer than the app can listen on those ports again. And
this is happening on 2 of the PCs that I use, both has windows xp with
sp2. Code is being written in native vc++ 2k5.
Regards,
-ab.
--
Steve Alpert
my email fgrir.nycreg @ tr.pbz is encrypted with ROT13 (www.rot13.org) and
spaces
.
- Prev by Date: Re: WHy is C# so much slower than c++???
- Next by Date: Re: Huge Floating Point Error
- Previous by thread: Huge Floating Point Error
- Next by thread: Re: Nasty Problem
- Index(es):
Relevant Pages
|
