Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Cant reach login page - StuckThreadDetectionValve

Brian Goldberg
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 7, 2020

We keep on seeing this message

07-Jan-2020 23:57:14.407 WARNING [ContainerBackgroundProcessor[StandardEngine[Catalina]]] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadCompleted Thread [http-nio-8080-exec-14] (id=[33]) was previously reported to be stuck but has completed. It was active for approximately [127,330] milliseconds.

And our JIRA login page does not load.  The browser is just blank.  Every once in a while the page loads.

I increased the maxthread value to 1024 (from 150) in the server.xml file and restarted the server - no change.

1 answer

1 vote
Ali
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 21, 2020

same here... any advice?

Brian Goldberg
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 22, 2020

We found out the reason for the error.  It (and some other weird behavior) was due to the fact that both our JIRA and Confluence instances were not able to reach the "Server Base URL".  That was because the Docker containers running JIRA and Confluence had the ability to reach each other, but not the IP addr which resolved to the public DNS name.

The problem started when we configured "Application Links" in both JIRA and Confluence.  That made both app need to speak to their respective Server Base URLs.

We found out that the apps couldn't communicate to each other's public DNS names using curl, and running it from inside the Docker container of JIRA and Confluence.

So, make sure you can hit those Server Base URLs!

Suggest an answer

Log in or Sign up to answer