Documentation for JIRA 4.1. Documentation for other versions of JIRA is available too.
操作の実行中に時折 JIRA がフリーズしたように見える場合があります。そのような場合、スレッド ダンプ — Java 仮想マシン内で現在実行中のスレッドおよびプロセスに関する情報を含むログ — の取り込みを行います。スレッド ダンプの取得は非破壊プロセスであるため、稼働中のシステム上で実施することができます。本書では、スレッド ダンプの取り込みに必要な手順を説明します。
The steps necessary to retrieve the thread dump are dependant on the operating system JIRA is running in — please follow the appropriate steps:
ps -ef | grep java
keithb 910 873 1 17:01 pts/3 00:00:18 /usr/java/jdk/bin/java -Xms128m -Xmx256m -Xms128m -Xmx256m -Djava.awt.headless=true -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.awt.headless=true -Djava.endorsed.dirs=/tmp/atlassian-jira-enterprise-3.6-standalone/common/endorsed -classpath :
kill -3 <pid>
If you have trouble using kill - 3 <pid> to obtain a thread dump, try using jstack a java utility that will output stack traces of Java threads for a given process.
ps -ef | grep java
次のようなプロセスが見つかります。
adam 22668 0.3 14.9 1691788 903928 ? Sl Jan27 9:36 /usr/lib/jvm/java-6-sun-1.6.0.14/bin/java -Djava.util.logging.config.file=/home/adam/Products/installs/atlassian-jira-enterprise-4.0.1-standalone/conf/logging.properties -XX:MaxPermSize=256m -Xms128m -Xmx1048m -Djava.awt.headless=true -Datlassian.standalone=JIRA -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true -Dmail.mime.decodeparameters=true -Datlassian.mail.senddisabled=false -Datlassian.mail.fetchdisabled=false -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.endorsed.dirs=/home/adam/Products/installs/atlassian-jira-enterprise-4.0.1-standalone/common/endorsed -classpath /home/adam/Products/installs/atlassian-jira-enterprise-4.0.1-standalone/bin/bootstrap.jar -Dcatalina.base=/home/adam/Products/installs/atlassian-jira-enterprise-4.0.1-standalone -Dcatalina.home=/home/adam/Products/installs/atlassian-jira-enterprise-4.0.1-standalone -Djava.io.tmpdir=/home/adam/Products/installs/atlassian-jira-enterprise-4.0.1-standalone/temp org.apache.catalina.startup.Bootstrap start
2. Run jstack <pid> to Capture a Single Thread Dump
This command will take one thread dump of the process id <pid>, in this case the pid is 22668, and log output to the file JIRAthreaddump.txt
adam@jiratrack:~$ jstack 22668 > JIRAthreaddump.txt
3. Take Multiple Thread Dumps
Typically you'll want to take several dumps about 10 seconds apart, in which case you can generate several dumps and output the stack traces to a single file as follows:
adam@jiratrack:~$ jstack 22668 >> JIRAthreaddump.txtdam@jiratrack:~$ jstack 22668 >> JIRAthreaddump.txtadam@jiratrack:~$ jstack 22668 >> JIRAthreaddump.txt