Wiki source code of Collect all the Tomcat's threads' stacks logs
Last modified by Aurelie Bertrand on 2022/02/15 18:04
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
1.1 | 1 | {{ddtoc/}} |
| 2 | |||
| 3 | ---- | ||
| 4 | |||
| 5 | = Introduction = | ||
| 6 | |||
| 7 | In some blocking case, it could be useful to collect all the logs of the Tomcat threads for investigation purpose. | ||
| 8 | |||
| 9 | This procedure explain how to do it. | ||
| 10 | |||
| 11 | (% class="box errormessage" %) | ||
| 12 | ((( | ||
| |
5.1 | 13 | Following this procedure may freeze the DigDash Enteprise application for a few seconds. |
| |
1.1 | 14 | This procedure should only proceed on the recommendation of a DigDash consultant. |
| 15 | ))) | ||
| 16 | |||
| 17 | = Collect all the logs (for Unix servers) = | ||
| 18 | |||
| |
6.1 | 19 | 1. The server is in a situation that demands to restart it |
| |
3.1 | 20 | 1. Get the Tomcat's PID (process id) using ##ps##, ##htop##, or any other tool |
| |
2.1 | 21 | 1. On the command prompt, execute the following : |
| |
3.1 | 22 | {{code language="unix"}}kill -3 <Tomcat PID>{{/code}} |
| 23 | 1. Retrieve **##catalina.log ##**(or **##catalina.out##**) file to communicate to the technical team. | ||
| |
1.1 | 24 | |
| 25 |