When troubleshooting various problems on the Content Gateway one might need to capture a Java thread dump. This KB article explains how to do that using jstack. If you do not have jstack installed, then you should be able to install it on CentOS 7 via the epel repo with: yum install java-latest-openjdk-devel -y
Instructions
Find out the PID of the Content Gateway process by running this command
| Code Block |
|---|
ps aux | grep [c]loudgateway.pid | awk '{ print $2 }' |
Capture the thread dump using jstack by running this command using the PID determined at step 1
| Code Block |
|---|
jstack PID > thread_dump.out |
If the above command does not capture anything, try running this:
| Code Block |
|---|
jstack -F PID > thread_dump.out |
Related articles
| Filter by label (Content by label) |
|---|
| showLabels | false |
|---|
| max | 5 |
|---|
| spaces | com.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@957 |
|---|
| showSpace | false |
|---|
| sort | modified |
|---|
| showSpacetype | falsepage |
|---|
| reverse | true |
|---|
| typelabels | pagejstack contentgateway |
|---|
| cql | label in ( "contentgateway" , "jstack" ) and type = "page" and space = "KB" | labels | jstack contentgateway |
|---|
|
