Information

Title	Why does error "TCP/IP connection to remote system closed, reason code 2" cause E3COMSERV to fail?

Summary	This article explains why receiving the error message "TCP/IP connection to remote system closed, reason code 2" can cause the E3COMSERV communication job to fail and provides some advice on how to prevent this situation from occurring.

URL Name	Why-does-error-TCP-IP-connection-to-remote-system-closed-reason-code-2-cause-E3COMSERV-to-fail

Resolution

E3COMSERV is the primary communication job that allows transactions between the Advanced Replenishment PC based Client and AS/400 or ISeries Server to take place
The job relies on a dedicated TCP/IP port (default 7100) for these transactions to take place
If the dedicated TCP/IP port receives unrecognizable traffic or is closed, the E3COMSERV job will automatically be terminated to prevent database corruption
The TCPIP configuration on the system should be reviewed by the network system administrator to audit the traffic being directed to the dedicated TCP/IP port

Products	Advanced Store Replenishment Client Server; Advanced Warehouse Replenishment Client Server

Module

Version	ALL

Error Message Code

Error message: "TCP/IP connection to remote system closed, reason code 2"

Cause

There are three possible causes for the E3COMSERV job to fail when the TCP/IP connection to remote system is closed.

Reason Code 2: The retry threshold (R2) defined in CHGTCPA has been reached. TCP has retransmitted the same packet R2 times (which is normally 16). TCP has determined the connection has been lost and closes the connection
Keepalive packets are not being transmitted across the network
The firewall is dropping transmitted 'keepalive' packets

Additional Information

Further information on the cause of the error can be found at the following IBM link: http://www-912.ibm.com/s_dir/SLKBase.nsf/0/dce52e8dee822d1d86256d040064def4?OpenDocument
To determine why a TCP keepalive is not responded to, a sniffer or Wireshark trace would need to be run at various points in the network. This would show how far the keepalive packets get, or if a response was sent back from the remote system (e.g. Reason Code 2: Determine why the remote host is unreachable)
If the messages are constant and contain the same TCP/IP address over and over again, these can be caused by a WRITER trying to print to a TCP/IP printer that is down or off-line. The WRITER attempts to connect by sending SYN packets, which the remote host never responds to, and the R2 threshold is reached. Holding the WRITER will suppress the messages until the problem with the printer is resolved
The TCP2617 message ID is elusive at times. When customers make changes to IP devices, there can be some "leftover" or "phantom" definitions for servers found in iNav under My Connections or under Management Central under ENDPOINTS that should be deleted
JDA recommends that you contact IBM support for assistance with system configuration
JDA Cloud Services is available to host JDA applications for customers as an alternative to a customer supporting their own internal systems

Publication Status	Published

Why does error "TCP/IP connection to remote system closed, reason code 2" cause E3COMSERV to fail?