-
Suggestion
-
Resolution: Fixed
-
None
NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? See the corresponding suggestion.
Adding this parameter to the server.xml will log stuck threads in the catalina.out:
<Valve className="org.apache.catalina.valves.StuckThreadDetectionValve" threshold="60" />
This will log any request thread (eg http thread) that has been processing for more than 60 seconds. This will not log background threads, eg scheduled jobs or any long running operation that processes in the background, like import/export, reindex etc.
If you are expecting to see something in these logs that you do not, that does not mean it is not running for more than 60s. It likely just means it is not running in a request thread. Thread dumps over time are still the best way to diagnose long running threads.
- is related to
-
CONFSERVER-40977 Ship Tomcat's long running (stuck) thread logging by default
- Closed
-
JRACLOUD-60546 Ship Tomcat's long running (stuck) thread logging by default
- Closed
[CONFCLOUD-40977] Ship Tomcat's long running (stuck) thread logging by default
Workflow | Original: JAC Suggestion Workflow [ 3408930 ] | New: JAC Suggestion Workflow 3 [ 3625748 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Confluence Workflow - Public Facing v3 [ 2250684 ] | New: JAC Suggestion Workflow [ 3408930 ] |
Workflow | Original: Confluence Workflow - Public Facing v3 - TEMP [ 2146742 ] | New: Confluence Workflow - Public Facing v3 [ 2250684 ] |
Workflow | Original: Confluence Workflow - Public Facing v3 [ 1904510 ] | New: Confluence Workflow - Public Facing v3 - TEMP [ 2146742 ] |
Workflow | Original: Confluence Workflow - Public Facing v2 [ 1801532 ] | New: Confluence Workflow - Public Facing v3 [ 1904510 ] |
Description |
Original:
Adding this parameter to the server.xml will log stuck threads in the catalina.out: {code}<Valve className="org.apache.catalina.valves.StuckThreadDetectionValve" threshold="60" /> {code} This will log any request thread (eg http thread) that has been processing for more than 60 seconds. This will not log background threads, eg scheduled jobs or any long running operation that processes in the background, like import/export, reindex etc. If you are expecting to see something in these logs that you do not, that does not mean it is not running for more than 60s. It likely just means it is not running in a request thread. Thread dumps over time are still the best way to diagnose long running threads. |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *Confluence Cloud*. Using *Confluence Server*? [See the corresponding suggestion|http://jira.atlassian.com/browse/CONFSERVER-40977]. {panel} Adding this parameter to the server.xml will log stuck threads in the catalina.out: {code}<Valve className="org.apache.catalina.valves.StuckThreadDetectionValve" threshold="60" /> {code} This will log any request thread (eg http thread) that has been processing for more than 60 seconds. This will not log background threads, eg scheduled jobs or any long running operation that processes in the background, like import/export, reindex etc. If you are expecting to see something in these logs that you do not, that does not mean it is not running for more than 60s. It likely just means it is not running in a request thread. Thread dumps over time are still the best way to diagnose long running threads. |
Link |
New:
This issue is related to |
Link |
New:
This issue is related to |
Project Import | New: Sat Apr 01 14:06:06 UTC 2017 [ 1491055566265 ] |