configured threshold for this StuckThreadDetectionValve is [120] seconds

[Benjamin Yu]

I saw this error:

and may be stuck (configured threshold for this StuckThreadDetectionValve is [120] seconds). There is/are [200] thread(s) in total that are monitored by this Valve and may be stuck.
java.lang.Throwable
at java.base@11.0.13/jdk.internal.misc.Unsafe.park(Native Method)
at java.base@11.0.13/java.util.concurrent.locks.LockSupport.parkNanos(Unknown Source)
at java.base@11.0.13/java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(Unknown Source)
at java.base@11.0.13/java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(Unknown Source)
at java.base@11.0.13/java.util.concurrent.CountDownLatch.await(Unknown Source)

When the number reached 200, jira crashed. How to fix this problem? How to increase the limit of valve or threshold?

Thank you.

[Claudio Casiello]

Hi we are experiencing the same issue. Any news?

[Luong La]

I got the same issue when ran Integrity checker
Error: "../secure/admin/IntegrityChecker.jspa] and may be stuck (configured threshold for this StuckThreadDetectionValve is [120] seconds).

jira v9.5.0 #950000-sha1:bfd830f
with
OS: Ubuntu 20.04
Java Version 11.0.17
Java VM OpenJDK 64-Bit Server VM
Apache Tomcat: 9.0.68
Database type and version: postgres 14.4
Database driver PostgreSQL JDBC Driver 42.5.1