Troubleshooting
Problem
A common misconception is to allocate JVM memory occupancy as a multiple of its maximum heap size.
Symptom
Getting OutOfMemory error, or even if not reaching that far, then still getting high CPU due to intense garbage collection activity.
[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"ARM Category":[{"code":"a8m50000000CdAmAAK","label":"WebSphere Application Server traditional-All Platforms-\u003EOutOfMemory-\u003ENative"}],"ARM Case Number":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"8.5.0;8.5.5;9.0.0;9.0.5"}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Historical Number
01753;L6Q;000 30117;999;000 68489;7TD;000 31665;L6Q;000
Was this topic helpful?
Document Information
Modified date:
03 March 2025
UID
swg21961513