StuckThreadDetectionValve.notifyStuckThreadCompleted
Asked by Ranjith K:

08-Nov-2020 16:58:08.639 WARNING \[ContainerBackgroundProcessor\[StandardEngine\[Catalina\]\] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadCompleted Thread \[http-nio-8080-exec-72\] (id=\[94\]) was previously reported to be stuck but has completed. It was active for approximately \[431,473\] milliseconds. There is/are still \[1\] thread(s) that are monitored by this Valve and may be stuck.

08-Nov-2020 16:58:08.641 WARNING \[ContainerBackgroundProcessor\[StandardEngine\[Catalina\]\]\] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadCompleted Thread \[http-nio-8080-exec-12\] (id=\[30\]) was previously reported to be stuck but has completed. It was active for approximately \[512,214\] milliseconds.


Answers:
author: Daniel Ebers
body: Hi Ranjith,

welcome to the Atlassian Community!

This error message is sometimes accompanied by performance issues and/or crashes of a Confluence instance. There is, indeed, a root cause to be found - but this is hard just from having this warning message at hand.

Do you see lags or crashes of your Confluence instance? Is this also applying to Jira (as you tagged Jira here)? Do you have both of them running on one server?

Did you upgrade recently to a newer version?  
Did you change Apps recently (upgrade/install)?

Although not knowing the specific setup it could also be a shortage of available memory.

Please also review this useful article:  
<https://confluence.atlassian.com/jirakb/common-causes-for-jira-server-crashes-and-performance-issues-203394749.html>

With some more information somebody here might be able to help you further.

Cheers,  
Daniel

comments: author: Nithyanantham Lakshmanan
body: We are also facing the same issue with Bamboo applications..

recently upgraded to 7.2.2.  

07-Nov-2021 20:37:29.028 WARNING \[ContainerBackgroundProcessor\[StandardEngine\[Catalina\]\]\] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadCompleted Thread \[http-nio-8085-exec-23242\] (id=\[19051481\]) was previously reported to be stuck but has completed. It was active for approximately \[450,749\] milliseconds. There is/are still \[6\] thread(s) that are monitored by this Valve and may be stuck.  
07-Nov-2021 20:37:29.028 WARNING \[ContainerBackgroundProcessor\[StandardEngine\[Catalina\]\]\] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadCompleted Thread \[http-nio-8085-exec-23257\] (id=\[19051675\]) was previously reported to be stuck but has completed. It was active for approximately \[388,376\] milliseconds. There is/are still \[5\] thread(s) that are monitored by this Valve and may be stuck.  
07-Nov-2021 20:37:29.028 WARNING \[ContainerBackgroundProcessor\[StandardEngine\[Catalina\]\]\] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadCompleted Thread \[http-nio-8085-exec-23241\] (id=\[19051479\]) was previously reported to be stuck but has completed. It was active for approximately \[450,854\] milliseconds. There is/are still \[4\] thread(s) that are monitored by this Valve and may be stuck.  
07-Nov-2021 20:37:29.028 WARNING \[ContainerBackgroundProcessor\[StandardEngine\[Catalina\]\]\] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadCompleted Thread \[http-nio-8085-exec-23280\] (id=\[19051712\]) was previously reported to be stuck but has completed. It was active for approximately \[168,154\] milliseconds. There is/are still \[3\] thread(s) that are monitored by this Valve and may be stuck.  
07-Nov-2021 20:37:29.028 WARNING \[ContainerBackgroundProcessor\[StandardEngine\[Catalina\]\]\] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadCompleted Thread \[http-nio-8085-exec-23279\] (id=\[19051710\]) was previously reported to be stuck but has completed. It was active for approximately \[179,266\] milliseconds. There is/are still \[2\] thread(s) that are monitored by this Valve and may be stuck.  
07-Nov-2021 20:37:29.028 WARNING \[ContainerBackgroundProcessor\[StandardEngine\[Catalina\]\]\] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadCompleted Thread \[http-nio-8085-exec-23286\] (id=\[19051723\]) was previously reported to be stuck but has completed. It was active for approximately \[113,549\] milliseconds. There is/are still \[1\] thread(s) that are monitored by this Valve and may be stuck.  
08-Nov-2021 09:24:30.048 INFO \[http-nio-8085-exec-23247\] org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request header  
Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level.  
java.lang.IllegalArgumentException: Invalid character found in method name \[0x160x030x010x020x000x010x000x010xfc0x030x030x110xdb\&0x16u0x910xeao0x030xf5\*d0x100xc3w0xd3Y0xb2BI0x1el0xe9b0xcd0xa40x8d0xef0xc20x9a0xd80xfa\]. HTTP method names must be tokens  
at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:432)  
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:502)  
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)  
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:818)  
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1626)  
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)  
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)  
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)  
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)  
at java.lang.Thread.run(Thread.java:748)  
08-Nov-2021 09:24:43.111 INFO \[http-nio-8085-exec-23188\] org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request header  
Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level.  
java.lang.IllegalArgumentException: Invalid character found in method name \[0x160x030x010x020x000x010x000x010xfc0x030x030x940D0xb1j\\L0x95\]. HTTP method names must be tokens  
at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:432)  
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:502)  
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)  
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:818)  


author: Dawn Fama
body: Same here JIRA Software Server 8.21.0


author: Daniel Ebers
body: Hi [@Dawn Fama](/t5/user/viewprofilepage/user-id/752917)

there can be many causes. I would suggest, like initially outlined, to start a extensive troubleshooting to get to the bottom of the cause.

First ideas give this knowledge base entry: <https://confluence.atlassian.com/jirakb/jira-is-unresponsive-threads-stuck-776812604.html>  

Regards,  
Daniel


author: SDLC Support
body: I am facing the same error in the logs.

04-May-2022 12:15:07.873 WARNING \[Catalina-utility-3\] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadDetected Thread \[https-jsse-nio-8443-exec-8\] (id=\[353\]) has been active for \[62,180\] milliseconds (since \[5/4/22 12:14 PM\]) to serve the same request for \[[https://confluence.res.sys.shared.fortis:8443/confluence/viewtracker/users.action?contentEntityId=83034199\&renderUserNames=true\&sort=\&startTimeStamp=\&atl_token=697d9bd121361b01bee995c273ef74032c66e4c0\&_=1651659244366](https://confluence.res.sys.shared.fortis:8443/confluence/viewtracker/users.action?contentEntityId=83034199&renderUserNames=true&sort=&startTimeStamp=&atl_token=697d9bd121361b01bee995c273ef74032c66e4c0&_=1651659244366)\] and may be stuck (configured threshold for this StuckThreadDetectionValve is \[60\] seconds). There is/are \[2\] thread(s) in total that are monitored by this Valve and may be stuck.  
java.lang.Throwable  
at java.net.SocketInputStream.socketRead0(Native Method)

Lot of slowness in the application.

I reviewed the page <https://confluence.atlassian.com/jirakb/common-causes-for-jira-server-crashes-and-performance-issues-203394749.html> , but dont find some relevant information related to confluence.

Also tried creating a support request from [Atlassian Support](https://support.atlassian.com/). It navigates me to [Confluence Data Center and Server support \| Confluence Server - latest \| Atlassian Support](https://support.atlassian.com/confluence-server/) , when I try to create bug report, it navigates me back to [Atlassian Support](https://support.atlassian.com/).

Is there a global support contact I can call?

Its urgent as prod users are impacted.

Thanks,

Saurabh

comments: author: Sloan
body: Hi Saurabh

I see one of the URLs in the first Stacktrace is related to our app Viewtracker. Have you seen any problems with Viewtracker? If so, please get in touch with us at support.bitvoodo.ch.

Best Regards  
Sloan


author: SDLC Support
body: Hi Sloan,

support.bitvoodo.ch. --\>Is this the support site for Atlassian?

I have a valid Atlassian license for confluence, but cannot contact Atlassian support , either via email or via phone.

Can you help?

Thanks,

Saurabh


Tags: confluence-server

jira

server