SAP Knowledge Base Article - Preview

3224648 - Idle network connection between two RFC Gateways is broken despite that gw/keepalive has a rather low value


An RFC destination (type 3 or type T at transaction SM59) is used to connect two systems.

After leaving the connection idle for some time, the RFC Gateway logs a network disconnection (e.g., "connection broken", "connection reset by peer" or "connection timed out") when there is a new attempt to send more data through this same destination / channel.

The disconnection happens despite that the value of the parameter "gw/keepalive" was set to a rather low value (like 60 or even 20), or after reducing the keepalive setting specific to the destination (at SM59, open the destination, switch to the "Special options" tab, "Keep-Alive Timeout" section).



  • SAP NetWeaver based product
  • ABAP Platform based product


ABAP platform all versions ; SAP NetWeaver all versions


connection broken, connection reset by peer, connection timed out, 238 , KBA , BC-CST-GW , Gateway/CPIC , BC-MID-RFC , RFC , BC-CST , Client/Server Technology , BC-NET , Network Infrastructure , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.