IT35215: SAPINPUT NODE LOSES INBOUND RFC CONNECTIONS

APAR status

• Closed as program error.

Error description

• When using the SAP Input Node, if a connection to the SAP
  server is broken in such a way that no FIN packet is
  transmitted then the underlying JCO listener does not detect
  that the connection is invalid. This causes a connection to be
  retained which can not receive messages and could lead to loss
  of throughput.
  
  This APAR adds a maximum idle timeout to SAP
  Inbound connections such that a connection will automatically
  be recycled if it has remained idle for a certain amount of
  times.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of IBM Integration Bus 10 and IBM App Connect
  Enterprise version 11 using the SAP Nodes.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  <span style="background-color:rgb(255, 255, 255)">When using the
  SAP Input Node, if a connection to the SAP </span><span
  style="background-color:rgb(255, 255, 255)">server is broken in
  such a way that no FIN packet is </span><span
  style="background-color:rgb(255, 255, 255)">transmitted then the
  underlying JCO listener does not detect </span><span
  style="background-color:rgb(255, 255, 255)">that the connection
  is invalid. This causes a connection to be </span><span
  style="background-color:rgb(255, 255, 255)">retained which can
  not receive messages and could lead to loss </span><span
  style="background-color:rgb(255, 255, 255)">of throughput.
                                                 </span><span
  style="background-color:rgb(255, 255, 255)">
  
  </span><span style="background-color:rgb(255, 255, 255)">
                              </span>
  

Problem conclusion

• <span style="background-color:rgb(255, 255, 255)">This APAR adds
  a maximum idle timeout to SAP </span><span
  style="background-color:rgb(255, 255, 255)">Inbound connections
  such that a connection will automatically  </span><span
  style="background-color:rgb(255, 255, 255)">be recycled if it
  has remained idle for a certain amount of times.
  
  To enable an idle timeout on SAPInput Node JCO connections set
  the environment variable:</span>
  
  <span style="background-color:rgb(230, 255, 237);color:rgb(3,
  47, 98);font-family:sfmono-regular,consolas,liberation
  mono,menlo,monospace">MQSI_SAP_IDLE_JCO_INBOUND=1</span>
  <span style="background-color:rgb(255, 255, 255)">  </span>
  By default the idle timeout period is 1 hour however this can be
  customised by setting the environment variable:
  
  <span style="background-color:rgb(230, 255, 237);color:rgb(3,
  47, 98);font-family:sfmono-regular,consolas,liberation
  mono,menlo,monospace">MQSI_SAP_IDLE_JCO_INBOUND_TIMEOUT=<time_in
  _milliseconds></span>
  
  In order to take effect environment variables must be set prior
  to Integration Node startup and must be visible to the
  Integration node's command shell. A restart of the Integration
  Node is required for any changes to take effect.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v10.0      10.0.0.24
  v11.0      11.0.0.12
  
  The latest available maintenance can be obtained from:
  http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
  
  If the maintenance level is not yet available,information on
  its planned availability can be found on:
  http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
  ---------------------------------------------------------------
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  INTEGRATION BUS

• Fixed component ID

  5724J0540

Applicable component levels