![]() Adding additional information showing which threads are consuming the most CPU may considerably expedite the troubleshooting process. With this information, we can now see which threads are consuming the most CPU and relate with what's being performed by each, as reported in the thread dumps Ītlassian Support may request thread dumps when troubleshooting JIRA application.NID in thread dumps is in hexadecimal, so you will need to convert decimal to hexadecimal to identify those threads The top window always shows a list of the currently active processes, including the names of their. ![]() Notice that the thread ID (TID) in Process Explorer is in Decimal format and corresponds to NID in the thread dumps. The Process Explorer display consists of two sub-windows. The first column is the thread ID (TID) and the second column is the CPU utilization for each thread. Go to the Threads tab to get an overview of the running threads within the process.Right-click the process and select Properties.Locate the tomcat.exe process, which is the application server that serves JIRA application.This is a third-party application, and as such it's not supported by Atlassian. Download Process Explorer and run it on the server JIRA application is installed.Another option for a high level overview is Using jvmtop to analyze JIRA performance. Windows Task Manager serves a purpose, but we recommend you replace it with Process Explorer for many reasons. įor *nix system please see Troubleshooting Jira performance with Thread dumps. This will only work for Windows systems and requires the use of a third-party application. You'll need to collect thread dumps and correlate that with the thread IDs from Process Explorer. ![]() This article outlines a way to analyze JIRA application performance using Process Explorer on Windows.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |