This article describes the diagnostics to collect when MFT Command Center or Internet Server is using High CPU. TIBCO Support will need the diagnostic information from the thread or threads that are using high CPU.

This article provides details on the diagnostics TIBCO Support will need to troubleshoot high CPU issues

All environments

Identify the JAVA Thread that is using the CPU

Windows:
    - Download and execute "Process Explorer" on the Windows server where MFT is using high CPU
    - Locate the MFT Java process in the left hand column of the "Process Explorer"
    - Right click on the MFT Java process and then click on "Properties"
    - In the "Properties" window click on the "Threads" tab (the threads tab has a column for CPU)
    - When the problem reoccurs, identify the thread IDs (TID) that are at or near 100%
    - Take a screenshot of the Process Explorer

UNIX:
    - Execute command: top -H |grep java
      Let this run for about 20 seconds.
      This will tell us the Java threads that are using the most CPU. 
      In most cases this will point to the looping threads.
    - Take a screenshot of the top command output

Execute jstack command to get a stack trace of all threads
    - Run the following command from a command prompt to verify that jstack is working:

      jstack -l pid

      Note: Replace pid with the actual pid of the java process.
      On Windows the pid is displayed in a column on the main "Process Explorer" screen and
      at the top of the "Properties" window.
      On Unix use "ps -edf" to get the pid

Note: The jstack command must be run with under the same user that started MFT and it must be using the same JAVA version that the MFT is executing under.

    - Once you have verified that the jstack command is working, press ctrl-c to stop the command
    - Run the following command from a command prompt to save the jstack dump in a file:

      Windows: jstack -l pid > c:\temp\jstack.txt
      UNIX: jstack -l pid > /tmp/stack.txt

      The jstack dump file should be about 36k or larger

TIBCO Support may ask for MFT and SSH tracing

    - When the problem starts happening, enable tracing under "Administrator"/"System Configuration".
    - Expand the "Remote Settings" section for the IS having the problem.
    - Under "SSH Trace Type", put a check in both "SSH Client" and "SSH Server" boxes.
    - Set "SSH Trace Level" "All Messages"
    - Set "Trace Level" to "All Messages"
    - Click "Update"
    - Let the tracing run for a few minutes and then disable tracing.

Upload the following debugging information

    - The jstack.txt output
    - Screenshot of the Process Explorer or top -H screens that show threads consuming the most CPU
    - The <mft install dir>\logs\trace folder
    - The <mft install dir>\server\logs folder