Blocked port after process kill

From: Andreas Höschler (ahoesch_at_smartsoft.de)
Date: 10/26/05

  • Next message: Hirchert, Dale L: "Solaris 9 vs Solaris 10 comparisons" 
    Date: Wed, 26 Oct 2005 16:40:44 +0200
To: sunmanagers@sunmanagers.org

    Dear managers,

    I have a process that opens a socket (port 61000). Sometimes this
    process stops working (we already have a clue why, still
    investigating...). If we kill the process and try to restart it we get
    an error message telling us that socket 61000 could not be bound. After
    waiting 4-6 minutes it works again. Is this normal? It seems that the
    port is freed by the OS after some timeout, but not immediately as a
    result of the process kill. Question: Can we force the OS to free the
    port explicitly or how can we make sure that the OS frees it
    immediately when the corresponding process is killed?

    Thanks a lot!

    Regards,

       Andreas
    _______________________________________________
    sunmanagers mailing list
    sunmanagers@sunmanagers.org
    http://www.sunmanagers.org/mailman/listinfo/sunmanagers

  • Next message: Hirchert, Dale L: "Solaris 9 vs Solaris 10 comparisons"

    Relevant Pages

    • Re: How to "kill" a tcp port...
      ... >> the OS will kill it. ... >> What I don't understand is that your netstat shows the port was ... I can't find that process ID in Task Manager either and it ...
      (microsoft.public.dotnet.languages.csharp)
    • Re: How to "kill" a tcp port...
      ... >> the OS will kill it. ... >> What I don't understand is that your netstat shows the port was ... I can't find that process ID in Task Manager either and it ...
      (microsoft.public.dotnet.framework)
    • Re: How to "kill" a tcp port...
      ... >> the OS will kill it. ... >> What I don't understand is that your netstat shows the port was ... I can't find that process ID in Task Manager either and it ...
      (microsoft.public.dotnet.general)
    • Re: Killing Sockets
      ... > port. ... > socket still remains. ... > Python app until it had done so. ... Not being sure of the context or nature of your $ kill (or the Python ...
      (comp.os.linux.networking)
    • Re: Problem with socket
      ... Be aware that those port numbers are part of the IANA-assigned range. ... socket operations on sockets for which there are no handles... ... The result of using comma lists is ... you have used the completely meaningless word "crash" to describe your ...
      (microsoft.public.vc.mfc)