PM95190: Websphere dynamic cache instances cannot be mapped to different dynamic map instances in Websphere eXtreme Scale.

APAR status

• Closed as program error.

Error description

• Websphere Dynamic Cache instances cannot be mapped to different
  dynamic map instances in WebSphere Extreme Scale
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All WebSphere eXtreme Scale dynamic cache   *
  *                  users who want to have multiple cache       *
  *                  instances with the same name correspond to  *
  *                  different maps within the same data grid.   *
  ****************************************************************
  * PROBLEM DESCRIPTION: Dynamic cache instances with the same   *
  *                      name but different application server   *
  *                      JVMs cannot use the same data grid      *
  *                      instance.                               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  With WebSphere eXtreme Scale,  multiple WebSphere Application
  Server application server JVMs might need to use the same data
  grid instance.
  Using the same data grid instance can be problematic if the
  different application server JVMs do not want to share the same
  data.   With the default dynamic cache instance (baseCache),
  this limitation is a problem because you cannt change the name
  of this cache instance within the application server.
  

Problem conclusion

• The com.ibm.websphere.xs.dynacache.cache_name cache custom
  property was introduced.  The value of this
  property is used as the name of the cache within the
  data grid.   For example, if you have two application servers,
  you can use this custom
  property to configure the baseCache instances to
  correspond to separate maps within the data
  grid. For example, you might use the names baseCache1,
  baseCache2, and so on.
  

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

  WS EXTREME SCAL

• Fixed component ID

  5724X6702

Applicable component levels

• R850 PSY

     UP