Jira - StuckThreadDetectionValve

Chris Thirst January 4, 2021

Hallo,

we have a Jira and Confluence instance with around 1000 Users. Until today everything worked fine now we get a failure - catalina.out:

04-Jan-2021 18:09:48.354 WARNING [ContainerBackgroundProcessor[StandardEngine[Catalina]]] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadDetected Thread [h

ttp-nio-28281-exec-6] (id=[25]) has been active for [122,253] milliseconds (since [1/4/21 6:07 PM]) to serve the same request for [http://<jira-URL>:<jira-PORT>/] and may b

e stuck (configured threshold for this StuckThreadDetectionValve is [120] seconds). There is/are [4] thread(s) in total that are monitored by this Valve and may be stuck.

        java.lang.Throwable

After shutting down we get:

"Catalina-startStop-2" #68 daemon prio=5 os_prio=0 tid=0x00007fe7f03a2800 nid=0x27de waiting on condition [0x00007fe7c4591000]

   java.lang.Thread.State: WAITING (parking)

        at sun.misc.Unsafe.park(Native Method)

        - parking to wait for  <0x0000000724a19a40> (a java.util.concurrent.FutureTask)

        at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)

        at java.util.concurrent.FutureTask.awaitDone(FutureTask.java:429)

        at java.util.concurrent.FutureTask.get(FutureTask.java:191)

        at org.apache.catalina.core.ContainerBase.stopInternal(ContainerBase.java:1001)

        - locked <0x00000005c01d2678> (a org.apache.catalina.core.StandardHost)

        at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:226)

        - locked <0x00000005c01d2678> (a org.apache.catalina.core.StandardHost)

        at org.apache.catalina.core.ContainerBase$StopChild.call(ContainerBase.java:1439)

        at org.apache.catalina.core.ContainerBase$StopChild.call(ContainerBase.java:1428)

        at java.util.concurrent.FutureTask.run(FutureTask.java:266)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

        at java.lang.Thread.run(Thread.java:748)

Our Confluence uses the jira-crowd-Dict to log in. When Jira is "up" Conflunence throws the same errors and we can't log in.

When Jira is down we can log in with confluence and the users managed through Jira.

 

Thanks for any advice.

 

0 answers

Suggest an answer

Log in or Sign up to answer