Troubleshooting
Problem
This is the data gathering procedure for native Out Of Memory (OOM) errors for IBM WebSphere Application Server on Windows. If you know, or strongly suspect, that you have a native memory problem, or have been informed by an IBM support representative that you have a native memory problem, these are the steps to collecting the data needed for proper diagnosis of a root cause.
Symptom
Some indications that you have a native memory problem are as follows. If you have any uncertainty about these points you should contact an IBM support representative first.
- Failure to create/fork new operating system threads (messages in SystemOut.log)
- JVMDBG001 (malloc) errors in native_stderr.log
[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Out of Memory","Platform":[{"code":"PF033","label":"Windows"}],"Version":"9.0;8.5.5;8.5;8.0;7.0;6.1;6.0;5.1.1","Edition":"","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]
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.
Was this topic helpful?
Document Information
Modified date:
03 March 2025
UID
swg21313578