IT25331: BROKEN ODBC CONNECTION CAUSES ABEND WHEN REQUESTING SUPPORTED DATA TYPES

APAR status

• Closed as program error.

Error description

• When a message flow node first gets an ODBC database connection,
  it interrogates the database for information such as what data
  types are supported. If between making the initial connection
  and requesting the supported data type information the
  connection to the database is lost, the integration server may
  abend. If the abend file contains a call stack, the following
  methods will be seen near the top:
  
  ImbOdbcConnectionInfo::supportsDatatype
  ImbOdbcConnectionInfo::gatherTypeInformation
  
  This is more likely to occur when using the option to "Connect
  before flow starts" on the data source node, and the connection
  has been killed from the database side or by the network for
  being idle for too long.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of IBM App Connect Enterprise V11 and IBM Integration
  Bus v10 using ODBC.
  
  
  Platforms affected:
  z/OS, MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  When a message flow node first gets an ODBC database connection,
  it interrogates the database for information such as what data
  types are supported. If between making the initial connection
  and requesting the supported data type information the
  connection to the database is lost, the integration server may
  abend. If the abend file contains a call stack, the following
  methods will be seen near the top:
  
  ImbOdbcConnectionInfo::supportsDatatype
  ImbOdbcConnectionInfo::gatherTypeInformation
  
  The error handling is not checking whether a failure to obtain
  information from the database is due to the connection being
  lost, and it continues to use the invalid database connection
  handle.
  
  This is more likely to occur when using the option to "Connect
  before flow starts" on the data source node, and the connection
  has been killed from the database side or by the network for
  being idle for too long.
  

Problem conclusion

• The product now checks whether any database errors when
  gathering type information are due to the database connection
  being lost, and if that is the case an exception is now thrown.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v10.0      10.0.0.14
  v11.0      11.0.0.1
  
  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