PI53120: DATASOURCE CONNECTION POOL MINIMUMPOOLSIZE TO BE 0 BY DEFAULT FOR NEWLY CREATED DATASOURCES

8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as new function.

Error description

• Datasource Connection Pool minimumPoolSize has to be 0 by
  default for newly created datasources to help in draining off
  all the connections when the connection pool is not used for
  prolonged periods as part of maintanence activity. This can
  help avoid connections becoming stale.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Datasource Connection Pool              *
  *                      minimumPoolSize to be 0 by default      *
  *                      for newly created datasources           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The default value of  Minimum connections in the datasource
  Connection Pool has been changed to 0 (previously 1),
  which helps to drain off the connections when the server is
  idle or on maintanence for prolonged time periods and thus
  can prevent connections from becoming stale.
  This change applies only to newly created datasources. For all
  existing datasources their current value for the minimum
  connections will continue to remain the same.
  

Problem conclusion

• The WebSphere J2C component has been updated to use the
  default value of 0 for minimum connections settings for newly
  created datasources.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.9.  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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R850 PSY

     UP