Connection Terminations

Connection terminations can be triggered from both the client side and the server side

Connection Terminations from the Server Side

The following entries appear in the log file when a connection termination is triggered from the server side (if the local SAProuter is the client).

SAProuter Log File

Thu Jun 14 16:08:47 2007 CONNECT FROM C18/- host 10.66.66.90/24761 (host2.company.corp) Thu Jun 14 16:08:47 2007 CONNECT TO S18/10 host 10.21.83.41/3299 (host2) Thu Jun 14 16:08:47 2007 ESTABLISHED S18/10 Thu Jun 14 16:08:58 2007 DISCONNECT S18/10 host 10.21.83.41/3299 (host2)

The client issues the error message below.

Syntax

SAProuter Error Message

1. ************************************************************************  LOCATION    SAProuter 39.0 on 'host2'
   *  ERROR       connection to partner '10.21.72.60:3298' broken
   *
   *  TIME        Thu Jun 14 16:08:58 2007
   *  RELEASE     710
   *  COMPONENT   NI (network interface)
   *  VERSION     39
   *  RC          -95
   *  MODULE      nixxi.cpp
   *  LINE        4660
   *  DETAIL      NiIRead: P=10.21.72.60:3298; L=???
   *  SYSTEM CALL recv
   *  ERRNO       232
   *  ERRNO TEXT  Connection reset by peer
   *  COUNTER     17
   ***********************************************************************
   

End of the code.

Or

SAProuter Log File

Thu Jun 14 16:09:50 2007 CONNECT FROM C19/- host 10.66.66.90/24847 (host2.company.corp) Thu Jun 14 16:09:50 2007 CONNECT TO S19/11 host 10.21.72.60/3298 (ldp007) Thu Jun 14 16:09:50 2007 ESTABLISHED S19/11 Thu Jun 14 16:10:02 2007 DISCONNECT S19/11 host 10.21.72.60/3298 (ldp007) RST

The client issues the error message below.

Syntax

SAProuter Error Message

1. ***********************************************************************
   *  LOCATION    SAProuter 39.1 (SP3) on 'host1'
   *  ERROR       connection to partner '10.21.72.60:3298' broken
   *
   *  TIME        Thu Jun 14 16:10:02 2007
   *  RELEASE     710
   *  COMPONENT   NI (network interface)
   *  VERSION     39
   *  RC          -95
   *  MODULE      nixxi.cpp
   *  LINE        4660
   *  DETAIL      NiIRead: P=10.21.72.60:3298; L=10.66.66.90:24848
   *  SYSTEM CALL recv
   *  ERRNO       104
   *  ERRNO TEXT  Connection reset by peer
   *  COUNTER     10
   ***********************************************************************
   

End of the code.

Connection Terminations from the Client Side

The following entries appear in the log file when a connection termination is triggered from the client side (if the local SAProuter is the server).

Thu Jun 14 16:13:20 2007 CONNECT FROM C20/- host 10.66.66.90/24849 (host2.company.corp) Thu Jun 14 16:13:20 2007 CONNECT TO S20/12 host 10.21.83.41/3299 (host2) Thu Jun 14 16:13:20 2007 ESTABLISHED S20/12 Thu Jun 14 16:13:43 2007 DISCONNECT C20/12 host 10.66.66.90/24849 (host2.company.corp) RST

There is no error message with errInfo because the error is on the client side.

Background and Further Analysis

The DISCONNECT entry in teh log file tells you the side where the connection termination was triggered. You can use this information to find the node/program that first closed the connection. The trace file for this program contains more information on the cause of the connection termination.

In some cases, the connection between the two programs can be terminated without either side triggering the termination. For example, this is the case if two SAProuters with a direct TCP/IP connection both record that the other side triggered the connection termination. This means that an active network component between the two programs terminated the TCP/IP connection. The network component concerned is often a firewall or a router with an idle timeout. If this occurs, check the network.

The DISCONNECT log entry also tells you whether or not the connection was closed in a TCP/IP-compliant manner. 'RST' at the end of the line indicates and RDT package or a retransmit timeout. This means that the other side or an active network component between the two sides of the TCP/IP connection ended the connection incorrectly. This can be caused by the program crashing, the connection being closed to early at application level, or a firewall.