PM97317: eXtremeMemory (XM) may encounter memory leaks under certain scenarios.

APAR status

• Closed as program error.

Error description

• For maps enabled for eXtremeMemory, memory leaks
  within the eXtreme scale server may occur under certain
  conditions.  The leaks occur slowly and can lead to
  exhaustion of all memory configured with eXtremeMemory.  At
  which point, CWOBJ7930E messages appear in the logs and
  require a server restart.
  
  Here are some of the conditions that lead to memory leaks
  when eXtremeMemory is enabled:
  
  1) Customers using the flush, touch and invalidate ObjectMap
  APIs within a session transaction not using autocommit.
  2) Customers with security enabled which encounter
  object grid security exceptions.
  3) Customers performing transaction rollbacks via
  Session.rollback or via run-time errors leading to transaction
  rollbacks.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Customers that have enabled eXtremeMemory.  *
  ****************************************************************
  * PROBLEM DESCRIPTION: When eXtremeMemory is                   *
  *                      enabled, you may encounter              *
  *                      memory leaks under certain conditions.  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  For maps enabled for eXtremeMemory, memory leaks
  within the eXtreme scale server may occur under certain
  conditions.  The leaks occur slowly and can lead to
  exhaustion of all memory configured with eXtremeMemory.  At
  which point, CWOBJ7930E messages appear in the logs and
  require a server restart.
  Here are some of the conditions that lead to memory leaks
  when eXtremeMemory is enabled:
  1) Customers using the flush, touch and invalidate ObjectMap
  APIs within a session transaction not using autocommit.
  2) Customers with security enabled which encounter
  object grid security exceptions.
  3) Customers performing transaction rollbacks via
  Session.rollback or via run-time errors leading to transaction
  rollbacks.
  

Problem conclusion

• The memory leaks are fixed.
  

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