Wiki source code of How to get a thread dump

Last modified by colinw on 2021/09/10 22:40
Show last authors
1 In some circumstances, getting a thread dump of iSymphony is required, or can greatly assist troubleshooting efforts. A thread dump contains information about what tasks iSymphony is currently doing, and whether any of those tasks have stalled.
2
3 == Step-by-step guide ==
4
5 To get a thread dump, you'll need an SSH connection to the iSymphony server. Then, follow these steps:
6
7 1. (((
8 Determine the process id of iSymphony:
9
10 {{code}}
11 # cat /opt/isymphony3/server/iSymphonyServer.pid
12 {{/code}}
13
14 This will print the process id of iSymphony, if it is running. For example:
15
16 {{code}}
17 # cat /opt/isymphony3/server/iSymphonyServer.pid
18 12435
19 {{/code}}
20 )))
21 1. (((
22 Run the following command to instruct iSymphony to print a thread dump. Note that this //will not// shut down or restart iSymphony.
23
24 {{code}}
25 # kill -QUIT <pid_from_step_1>
26 {{/code}}
27
28 Be sure to replace <pid_from_step_1> with the actual value that was returned from the command in step 1. This command will cause iSymphony to log the current thread dump into its log files.
29 )))
30 1. Package your log files as described at [[doc:ISYMDOCS.Reporting Issues]], and send them to the iSymphony support team.
31
32 == Related articles ==
33
34 Related articles appear here based on the labels you select. Click to edit the macro and add or change labels.
35
36
37
38 {{contentbylabel spaces="" showLabels="false" reverse="true" sort="modified" max="5" labels="thread-dump deadlock" showSpace="false" type="page"/}}
39
40 {{details hidden="true"}}
41 |=(((
42 Related issues
43 )))|(((
44
45 )))
46 {{/details}}

Search

Navigation

iSymphony