PI22240: MEMORY OVERLOAD PROTECTION (MOP) CAN NO LONGER BE ENABLED/DISABLED ON A PER-CLUSTER BASIS

8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• RTC defect 133208 for inclusion 8553
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Currently MOP is defined at cell        *
  *                      level , not on cluster level so         *
  *                      whatever is defined on cell was         *
  *                      applicable for all clusters             *
  ****************************************************************
  * RECOMMENDATION:  This fix will introduce one cell level      *
  *                  property for defining MOP value at each     *
  *                  cluster seperately                          *
  ****************************************************************
  Currently MOP is defined at cell level , not on cluster level
  so whatever is defined on cell was applicable for all
  clusters. We need to segerate it on each cluster member so
  that we can have freedom to define different
  MOP limit for different cluster.
  

Problem conclusion

• This fix will introduce a new cell-level custom property
  mopPerClusterThresholds, which can define MOP values for each
  cluster member. For example, cluster1=80 cluster2=90. This
  custom property will be for internal use only and therefore
  will not be documented in the infocenter.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack x.x.x.x.  Please refer to the Recommended Updates
  page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R850 PSY

     UP