How to troubleshoot using TestWeb.war
If you can't follow the preceding troubleshooting procedure because the NSM is unresponsive, you can use the attached
TestWeb.war tool. The
TestWeb.war tool collects a heap dump for analysis. The tool also indicates whether you are experiencing a memory leak.
The dump location is noted in the
Emsout.log file. Logging is similar to the following:
2013-01-30 16:42:29,693 Initializing HeapDumper thread
2013-01-30 16:42:29,693 Initializing Heap Memory dump Thread
2013-01-30 16:42:48,553 Created HEAPDUMP file F:\heap\heap.bin
After the event occurs, collect the dump file by viewing the location in the
emsout file, and open a case with Technical Support:
- To install TestWeb.war:
- Download the TestWeb.war file attached to this article.
- Place the file into the <manager installation folder>\App\apache-tomcat\webapps folder.
- Click the NSM icon in the notification area and click Stop Manager.
- Click the NSM icon in the notification area and click Start Manager. You see a TestWeb folder. Wait for the issue to recur.
- Gather the files:
- View the emsout.log file for the location of the heap.bin file.
- Collect the heap.bin file.
- Deactivate TestWeb.war:
- Delete both TestWeb.war and the \TestWeb folder.
- Click the NSM icon in the notification area and click Stop Manager.
- Click the NSM icon in the notification area and click Start Manager.
- Provide the following information to your Technical Support contact:
- The heap.bin files
- The output of the InfoCollector utility
See KB59385 for further information about running InfoCollector.
NOTE: This tool is useful in-memory leak situations. But if you deploy it in a normal operational environment, it causes more overhead on the NSM.