Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-7463 Upgrade JGroups to 2.6.22
  3. JBPAPP-9588

FD_SOCK server socket is never closed after network interruption

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Major Major
    • EAP_EWP 5.2.0
    • EAP_EWP 5.1.2
    • Clustering
    • None
    • Release Notes
    • Hide
      JGroups FD_SOCK protocol did not set the <systemitem>TCP_KEEPALIVE</systemitem> option on the server side of the socket. After a network interruption during which the client side had broken the connection, the server side sockets remained open until the JGroups channel was shut down. The FD_SOCK protocol now sets the <systemitem>TCP_KEEPALIVE</systemitem> option on the server side of the socket. Now even if the client side of the socket is closed during a network interruption, the server side socket is closed by the <systemitem>TCP_KEEPALIVE</systemitem> timeout.
      Show
      JGroups FD_SOCK protocol did not set the <systemitem>TCP_KEEPALIVE</systemitem> option on the server side of the socket. After a network interruption during which the client side had broken the connection, the server side sockets remained open until the JGroups channel was shut down. The FD_SOCK protocol now sets the <systemitem>TCP_KEEPALIVE</systemitem> option on the server side of the socket. Now even if the client side of the socket is closed during a network interruption, the server side socket is closed by the <systemitem>TCP_KEEPALIVE</systemitem> timeout.
    • Documented as Resolved Issue
    • NEW

      The server side of the FD_SOCK socket is never closed after a network interruption during which the client side is closed.

      JGRP-195 added TCP keepalive to FD_SOCK, but only to the client side.

            rhn-support-dereed Dennis Reed
            rhn-support-dereed Dennis Reed
            Petr Penicka Petr Penicka (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: