|
| Problem | This document describes how to troubleshoot java.lang.OutOfMemoryError errors on a Windows® platform when you suspect a memory leak in the Native Heap. Base this action on your analysis of the documentation collected from the technote "MustGather: Out of Memory Errors on Windows, Part 1." | | | | Solution | This is the second step in gathering troubleshooting data when there is evidence of a memory leak. MustGather: Out of Memory Exceptions on Windows, Part 1 is a prerequisite, since it helps you decide if this technote is necessary.
If you already contacted support, continue to the component-specific MustGather information. Otherwise, click the following link: MustGather: Read First for all WebSphere Application Server Products.Out of memory (native memory) specific MustGather informationWindows includes a performance viewer (part of the Microsoft® Management Console) that can be used to determine which threads in a Java™ process are consuming memory.- From Start, select Programs > Administrative Tools > Performance Monitor.
Alternatively, from Start, select Settings > Control Panel, double-click on Administrative Tools, then double-click on Performance to open the Performance Monitor tool. - Expand Performance Logs and Alerts.
- Right-click Counter Logs, then choose New Log Settings.
- Type a log setting name.
- Click on Add to add counters.
- In the Performance Object window, select Object as Object.
- Click Select counter from List, then select these counters:
Counter = mutexes
Counter = semaphores
Counter = threads - Click on Add to add new properties.
- In the Performance Object window, select Object as Memory
- Select Select counter from List, then select these counters:
Counter = available Mbytes
Counter = page faults/sec
Counter = page reads/sec
Counter = page writes/sec - Click on Add to add new properties, then click on Close.
- Logging starts immediately.
- To end logging, right-click Log Name in the counter window, then click Stop.
- To review the log:
- Click the System Monitor in the left pane
- Click View Log File Date on the tool bar
- Select the log file name you want to see
- Collect the following data:
- For WebSphere Application Server V6.0 releases
- The server.xml file located in the install_root\profiles\profile_name\config\cells\cell_name\nodes\node_name\servers\server_name
- Everything in the install_root\profiles\profile_name\logs\server_name directory, specifically systemErr, systemOut, native_stderr and native_stdout logs are needed
- Everything in the install_root\profiles\profile_name\logs\ffdc directory
- All documents requested For all releases below
- For WebSphere Application Server V5.0 and V5.1 releases:
- The server.xml file located in the install_root\config\cells\nodes\node_name\servers\server_name directory, specifically systemErr, systemOut, native_stderr and native_stdout logs are needed
- Everything from the install_root\logs\server_name directory
- Everything from the install_root\logs\ffdc directory
- All documents requested For all releases below
- For WebSphere Application Server V4.0 and 3.5 releases:
- A XMLConfig full export.
- Everything from the install_root\logs directory from the WebSphere Application Server system, specifically stderr and stdout and tracefile files
- All documents requested For all releases below
- For all releases:
- Perfmon logs: Logs created by the performance tool.
- All javacore.txt files that were created when OutOfMemory conditions occurred. If javacore.txt files were created, you can find them in the install_root, install_root\bin or in the configured working directory
- Include the Application Server systemErr, systemOut, native_stderr, and native_stdout logs, if they are located in a different directory
- Follow instructions to send diagnostic information to IBM support.
For a listing of all technotes, downloads, and educational materials specific to the Out of Memory component, search the WebSphere Application Server support site. | |
| | | |
| |
|
Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, Out of Memory Operating system(s): Windows Software version: 3.5, 4.0, 5.0, 5.1, 6.0 Software edition: Advanced, Base, Network Deployment, Single Server Reference #: 1153585 IBM Group: Software Group Modified date: 2004-12-13
(C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.
|