java-initiated IPv6 Sockets Hanging in CLOSE_WAIT State

Clovertech Forums Read Only Archives Cloverleaf Cloverleaf java-initiated IPv6 Sockets Hanging in CLOSE_WAIT State

  • Creator
    Topic
  • #51656
    Bob Moriarty
    Participant

      5.6.2 on RedHat 4

      I’ve observed hundreds of these sockets in the CLOSED_WAIT state.

      Eventually, there’s a “java.io.IOException: Too many open files” failure.

      hciengine-initiated sockets (which are of type IPv4) disappear properly when disconnected.

      Bouncing the hostserver clears up the CLOSE_WAIT sockets and for a brief while, the IPv6 sockets function properly when disconnecting, i.e. they disappear instead of hanging in a CLOSE_WAIT state.

      I’ve attached some output from the “lsof -i tcp” command.

      Thanks in advance for any ideas or solutions.

      Also, and perhaps related, does anyone know why java opens IPv6 listeners and hciengine uses IPv4?

    Viewing 0 reply threads
    • Author
      Replies
      • #71132
        Bob Moriarty
        Participant

          After a little more investigation I see that the hanging CLOSE_WAIT socket  problem only occurs if Network Monitor is opened. It does not matter if the Netwaork Monitor tab is later closed. The socket used to connect the GUI with Network Monitor gets hung in a CLOSE_WAIT state.

          Also, I noticed that the display of my attachment (created with MS notepad.exe) gets mangled with IE7 but displays just fine with the Google Chrome browser.

      Viewing 0 reply threads
      • The forum ‘Cloverleaf’ is closed to new topics and replies.