StuckThreadDetectionValve entry in server.xml

[Jason Ferris]

my server.xml file that was running in previous version of JIRA in test 7.13.0 was fine. But when I updated to 8.5.3 I now have a warning that my server.xml file is not the same and may want to review it. The only change I can see is that my new one after updating does not have the  entry below. 

<Valve className="org.apache.catalina.valves.StuckThreadDetectionValve" threshold="120"/>

I am not familiar with what this entry does or fixes so I am not sure if I should re-add this to my current server.xml file. Can anyone shed light on this entry and would it helps with? Maybe the newer JIRA doesn't need this?

Thanks for any feedback!

[Bruno · Accepted solution]

Hi @Jason Ferris
Having this line in the server.xml file will help to identify in case any thread takes longer than 120 seconds to run.

It appends to catalina.out log file any long running thread, and having to many long running threads can point to performance issue.

Resumed: It helps on diagnostics. It is recommended to have it in the server.xml file.

This suggestion can help with some more details about it.
https://jira.atlassian.com/browse/JRASERVER-60546

Hope that helps.

[Jason Ferris]

Hi @Bruno  Thank you for the reply! I will go back and add this line into the server.xml file. This was in my test environment for upgrade procedure etc and will make sure this step is in the process once I update my production environment. 

[Jason Ferris]

Can anyone shed any light here or should I just go ahead and add this to my server.xml file?

[Jason Ferris]

I ended up just restarting JIRA without adding this line to my xml file. All seems to be fine, just not sure if that entry was to help performance in any way.