General tip for troubleshooting high CPU issues...
(1) Enable standard debug:
DEBUG_SHOW_TIMEOUT=1
DEBUG_CAPTURE_TIMEOUT=1
Debug_ThreadID=1
CONSOLE_LOG_ENABLED=1
(2) generate a manual NSD during the problem.
(3) To accompany the NSD, collect screenshots capturing the thread that is consuming the high CPU.
Windows:
Download and install "Process Explorer" from Microsoft (http://technet.microsoft.com/en-gb/sysinternals/bb896653.aspx)
Launch Process Explorer and do the following:
(1) doubleclick on the task(s) that is consuming the high CPU resources to display the task's details window in the bottom pane
(2) whilst still highlighting the task in the top pane, right click and open its properties and select the Thread's tab
(3) please take a screenshot of everything in the bottom and top window panes of the Process Explorer and another screenshot highlighting the task's Thread properties.
UNIX:(this example of for Linux)
Launch the following command
a. detect the process & pid by issuing the following Linux commands:
ps auxw | sort -r +2 | head -10
Run "top", then press K
You'll have the %CPU column organised. Obtain the PID that is consuming the most CPU.
Then run the following to get the Thread ID TID info for the process:
ps -p <pid> -L -o pid,tid,psr,pcpu
Send the data to IBM Support.
With this data at hand, IBM Support will be quickly able to isolate the specific thread that is causing the CPU spike and using the NSD, they can review the offending thread's call stack which can speed up time to resolution for your problem.
Regards,
Paul