PM71059: Entries in some asynchronous replica shards are not removed when you run the clear operation.

APAR status

• Closed as program error.

Error description

• Asynchronous replicas can have remaining entries after you run
  the clear operating on the primary shard.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of Websphere eXtreme Scale who    *
  *                  use ObjectMap.clear and use asynchronous    *
  *                  replicas or multimaster replication.        *
  ****************************************************************
  * PROBLEM DESCRIPTION: When clearing a map, some replicas      *
  *                      can still have entries in them, while   *
  *                      other map entires are correctly         *
  *                      cleared.                                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A window of time exists where a replica can report that it
  received a clear operation when it actually did not.  The fix
  for this problem puts in logic to handle this window of time.
  

Problem conclusion

• The fix for this problem was fixed in the 8.5 release.  The
  fix was back ported to the 7.1.1 release and is available as an
  interim fix.
  

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

• R711 PSY

     UP