IZ68122: DB2 3.53.70 JCC NOT CLEANING LOGWRITERS IN CASE OF CONNECTION FAILURE. LATER JCC REQUIRED.

APAR status

• Closed as program error.

Error description

• DB2 3.53.70 JCC not cleaning logwriters in case of connection
  failure. Later JCC required.
  
  The com.ibm.db2.jcc.b.ib holds on to 766,929,944 bytes of
  memory. It has a vector, apparently static variable, that holds
  on to 10,000+ of com.ibm.db2.jcc.t4.i objects.
  
  See IZ36247 JCC NOT CLEANING LOGWRITERS IN CASE OF CONNECTION
  FAILURE
  

Local fix

• Problem was first fixed in DB2 9.5 Fixpak 4. At minimum this
  fix should be applied to the client.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the IBM Data Server Driver for JDBC *
  *                 and SQLJ                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: JCC not cleaning logwriters in case of  *
  *                      connection failure.  This results in a  *
  *                      memory leak.  The memory leak also      *
  *                      occurs even with tracing disabled.      *
  *                                                              *
  *                                                              *
  *                                                              *
  *                                                              *
  *                                                              *
  *                      This DB2 problem appeared in JCC driver *
  *                      starting from version # 3.51.90         *
  *                      (shipped with DB2 V9.5 FP1) and above   *
  *                      and was first fixed in DB2 LUW V9.5     *
  *                      Fixpak 4 (s090429) under APAR IZ36247.  *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  *                                                              *
  *                                                              *
  *                                                              *
  ****************************************************************
  Prob was fixed under APAR IZ36247
  

Problem conclusion

• Problems fixed after DB2 LUW V9.5 Fixpack 3.  Upgrade to DB2
  LUW V9.5 Fixpack 4.  No changes to Maximo are needed to address
  this APAR.
  
  
  
  
  
  The fix for this APAR is contained in the following maintenance
  package:
  
    | release\fix pack | REL 7.1.0.0 - BS
  

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:

Modules/Macros

• MAXIMO
  

Fix information

• Fixed component name

  MAXIMO INSTALL

• Fixed component ID

  5724R46IT

Applicable component levels

• R710 PSY

     UP