Collecting information to troubleshoot high use of CPU or memory

1. Open a browser and log on to NSM. 
2. Press CTRL+N to open a duplicate window with a visible address bar.
3. In the address bar, edit the URL from https://localhost/intruvert/jsp/module/MainFrame.jsp to https://localhost/intruvert/jsp/diag/index.jsp.
    
4. Gather StacDump results:
   1.  Select StackDump.
   2.  Copy the displayed screen output to a text file.
       
5. Gather CPU use information:
   1. Select CPU use.
   2. Copy the displayed screen output to a text file.
       
6. Provide the following information to your Technical Support contact.
   • The text files of StackDump and CPU use
   • InfoCollector
   • Screenshot which indicates high CPU use of NSM service (java.exe)
   • The date and time that the information was obtained

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

1. To install TestWeb.war:
   1. Download the TestWeb.war file attached to this article.
   2. Place the file into the <manager installation folder>\App\apache-tomcat\webapps folder. 
   3. Click the NSM icon in the notification area and click Stop Manager. 
   4. Click the NSM icon in the notification area and click Start Manager. You see a TestWeb folder. Wait for the issue to recur.
        
2. Gather the files:
   1. View the emsout.log file for the location of the heap.bin file.
   2. Collect the heap.bin file.
       
3. Deactivate TestWeb.war:
   1. Delete both TestWeb.war and the \TestWeb folder.
   2. Click the NSM icon in the notification area and click Stop Manager.
   3. Click the NSM icon in the notification area and click Start Manager.
       
4. Provide the following information to your Technical Support contact:
   1. The heap.bin files
   2. 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.