PM80923: When you run a query on a hash index with eXtremeMemory enabled, a memory leak occurs.

APAR status

• Closed as program error.

Error description

• WebSphere eXtreme Scale values are not removed appropriately
  when you use eXtremeMemory.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  WebSphere eXtreme Scale users who have      *
  *                  enabled eXtremeMemory and use the built-in  *
  *                  HashIndex plug-in.                          *
  ****************************************************************
  * PROBLEM DESCRIPTION: If you enable eXtremeMemory and use     *
  *                      the built-in HashIndex plug-in, a       *
  *                      container might experience a            *
  *                      segmentation fault.                     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  This container failure only happens if you remove entries
  from a map while simultaneously running index queries
  on the map.  This problem can be avoided by not running index
  queries while entries are being removed from the same map.
  This problem can be recognized by a container disappearing and
  leaving a Java core file in its working directory.  The Java
  core file contains a stack trace that goes through one of the
  find methods on the HashIndex class.
  

Problem conclusion

• You can avoid this issue by not running index queries while
  removing entries from the same map.
  

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

• R860 PSY

     UP