PK65810: ERROR "THE CONNECTION CACHE OF THIS CACHE NAME ALREADY EXISTS" WHEN APPLICATION IS RECYCLED

Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• This problem occurs when application uses Oracle FCF
  configuration and the application calls setLogWriter method for
  the datasoure.
  
  java.sql.SQLException was detected : The connection cache of
  this cache name already exist
  DSRA0010E: SQL state = null  Error Code = 17,140
  
  Above error occurs when application is recycled.
  

Local fix

• Not to call setLogWriter method for datasource.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All IBM WebSphere Application Server        *
  *                  V6.0.2 and V6.1 users of Oracle FCF.        *
  ****************************************************************
  * PROBLEM DESCRIPTION: Oracle cache name already exist error   *
  *                      when using setLogWriter()               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The following error will occur when using Oracle FCF and
  setLogWriter()
  
  java.sql.SQLException was detected : The connection cash of this
  cash name already exist
  DSRA0010E: SQL state = null  Error Code = 17,140
  

Problem conclusion

• When Oracle FCF is used and setLogWriter() is called, a new
  instance of the cache will be created and the already exist
  error will not occur.
  
  The fix for this APAR is currently targeted for inclusion in
  fix packs 6.1.0.19 and 6.0.2.31.  Please refer to the
  Recommended Updates page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

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

  WEBSPH APP SERV

• Fixed component ID

  5724J0800

Applicable component levels

• R60A PSY

     UP

• R60H PSY

     UP

• R60I PSY

     UP

• R60P PSY

     UP

• R60S PSY

     UP

• R60W PSY

     UP

• R60Z PSY

     UP

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61P PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP