PI24706;8.5.5: Memory Overload protection (MOP) value is not persistent after s

Download Description

PI24706 resolves the following problem:

ERROR DESCRIPTION:
Memory Overload protection (MOP) configuration property value is not reflecting after server restart. The changed value of Memory Overload protection (MOP) value is taking effect at runtime not after server/dmgr restart.

LOCAL FIX:

PROBLEM SUMMARY

USERS AFFECTED:
All users of IBM WebSphere Application Server

PROBLEM DESCRIPTION:
After server restart, the Memory Overload protection (MOP) value is not preserved.

RECOMMENDATION:
None

Memory Overload protection (MOP) value cannot be retained after server restart. Since some variables are using the Memory Overload protection (MOP) value to calculate other
percentages this will lead to an incorrect calculation and further it might lead to unnecessary calls to garbage collection (gc) and will increase CPU overhead or other major issues.

PROBLEM CONCLUSION:
The Memory Overload protection (MOP) value is now initialized to the last set value and is now persistent after server restart.

The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.4. Please refer to the recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980