Troubleshooting
Problem
The WebSphere Application Server Java Proxy and Java On Demand Router use an asynchronous thread to write log entries to files such as the proxy.log to improve request/response performance. If there is a disk or network filesystem issue, log entries asynchronously queued in native memory may accumulate and consume excessive native memory.
Symptom
Native OutOfMemoryError (OOM) on 32-bit or exhausted physical memory and paging on 64-bit.
[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Proxy server","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF012","label":"IBM i"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"8.5.5;8.5;8.0;7.0","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
swg21690814