PM53147: WebSphere Application Server might use the default dynamic cache provider, instead of the defined provider in eXtreme

APAR status

• Closed as program error.

Error description

• If WebSphere Application Server is configured to use the
  WebSphere eXtreme Scale dynamic cache provider and is started
  before the WebSphere eXtreme Scale data grid is available, then
  the default dynamic cache provider is used instead, and a local
  cache is created.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of the WebSphere eXtreme Scale    *
  *                  dynamic cache provider                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: When WebSphere Application Server       *
  *                      starts before the eXtreme Scale         *
  *                      data grid is available, the default     *
  *                      cache might be used.                    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  If the WebSphere eXtreme Scale data grid is not started and
  available when WebSphere Application Server is started, the
  default WebSphere Application Server dynamic cache provider is
  used to create a WebSphere Application Server dynamic cache
  local to the WebSphere Application Server JVM and
  does not connect with the eXtreme Scale data grid when it is
  available.
  The following message is displayed in the logs:
  DYNA1066E: Unable to initialize the cache provider <  >.
  The Dynamic cache will be used to create the cache instance
  <  > instead of the configured cache provider.
  

Problem conclusion

• The eXtreme Scale provider code has been changed to determine
  whether the data grid is connected when WebSphere
  Application Server starts and to retry the connection until one
  can be made, rather than allowing the default WebSphere
  Application Server dynamic cache provider to create a local
  cache.
  
  Until the eXtreme Scale data grid is available, the dynamic
  cache client remains in fast-fail mode, where all
  invocations (put, get, invalidate) are a no-op and return
  "null" where appropriate.
  

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

  XD EXTREME SCAL

• Fixed component ID

  5724J3402

Applicable component levels

• R710 PSY

     UP