IT29503: JDBC SYBASE CONNECTION NOT BEING MARKED BROKEN AFTER SQLSTATE 08W01

APAR status

• Closed as program error.

Error description

• If there are active JDBC connections to a Sybase database
  server when that server is shut down, possibly for maintenance,
  the next time the connection is used by a message flow it does
  not mark the connection as broken after receiving the following
  SQL exception information:
  
  
  SQLSTATE: 08W01
  SQLCODE: -100
  Native error code: 7950
  
  
  A BIP4361W warning message may be written to the system log ,
  and if using JDBC connection pooling, subsequent calls to
  getJDBCType4Connection() might repeatedly fail with the
  following recoverable exception:
  
  
  BIP6267E: There has been a problem establishing a connection to
  the JDBC provider ''myJDBCProvider'' in node
  ''myJavaComputeNode''. Exception details:
  'java.sql.Connection=null'
  
  To recover, the integration server has to be restarted.
  
  
  Additional Symptom(s) Search Keyword(s):JDBC, SYBASE,
  Connection, Broken, SQLSTATE 08W01
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of IBM Integration Bus V10 and IBM App Connect
  Enterprise V11 using JDBC connections to a Sybase database
  server.
  
  
  Platforms affected:
  z/OS, MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  If there are active JDBC connections to a Sybase database server
  when that server is shut down, possibly for maintenance, the
  next time the connection is used by a message flow it does not
  mark the connection as broken after receiving the following SQL
  exception information:
  
  SQLSTATE: 08W01
  SQLCODE: -100
  Native error code: 7950
  
  A BIP4361W warning message may be written to the system log, and
  if using JDBC connection pooling, subsequent calls to
  getJDBCType4Connection() might repeatedly fail with the
  following recoverable exception:
  
  BIP6267E: There has been a problem establishing a connection to
  the JDBC provider ''myJDBCProvider'' in node
  ''myJavaComputeNode''. Exception details:
  'java.sql.Connection=null'
  
  To recover, the integration server has to be restarted.
  

Problem conclusion

• The product now recognises some additional Sybase database
  return codes to mean that the JDBC connection is broken.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v10.0      10.0.0.18
  v11.0      11.0.0.6
  
  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