Results 1 to 2 of 2
  1. #1
    the_shackler is offline Member
    Join Date
    Jul 2009
    Posts
    1
    Rep Power
    0

    Default Sockets, IOExceptions, and What's different with Linux

    Hello all -

    This my first post here. I have ran into a bit of an issue with some code I have written. I have written a small client/server application that works on the premise that if the remote application ends, the socket will be broken, and an IOException will be thrown. I then catch the IOException and then end the particular thread associated with that socket. This works fine in Windows, but when I kill the remote application in Linux, an IOException is never thrown on the server, it's as if the socket is still there even tho the application ended. I'm thinking there is something different that happens when I kill a process in Linux vs Windows. I have tried using the SIGINT, and SIGTERM switches for kill but they made no difference. Does anyone have any idea, admittedly I am a Linux noob, thanks!

    -Kam

  2. #2
    parul1234 is offline Member
    Join Date
    Jul 2009
    Posts
    4
    Rep Power
    0

    Default

    did you put wait to wait for the termination of the other process .. It may be reason that you are killing unix process and it become zombie process . Process on unix need to be killed properly

Similar Threads

  1. Replies: 6
    Last Post: 04-08-2009, 05:05 AM
  2. Sockets NIO
    By aamp in forum New To Java
    Replies: 3
    Last Post: 01-15-2009, 11:56 AM
  3. Sockets
    By Zosden in forum Networking
    Replies: 16
    Last Post: 05-27-2008, 05:55 PM
  4. IOExceptions and missing JavaDoc
    By tim in forum NetBeans
    Replies: 0
    Last Post: 01-29-2008, 01:55 PM
  5. Help with Sockets
    By Eric in forum Networking
    Replies: 3
    Last Post: 12-01-2007, 09:09 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •