Freeze / Stuck when someone login

Rui December 25, 2018

Hi I want to set up the Confluence and Jira SD behind Apache server (single server) using mod_proxy module

My server configuration is as follows:

my.company.com (HTTP)

    Apache 2.4.37 on Windows Server 2019

        - Confluence (localhost:8090 = my.company.com) (v6.13)

        - Jira Service Desk (localhost:8080 = my.company.com/track ) (v7.13)

 

 

Problem:
  When someone(not particular user) login (or websudo)  to Confluence server, the screen stucks and cannot login.  

 

What I know:

 - Confluence uses Jira user directory
 - Configured server.xml and httpd.conf
 - I can access to both instances remotely
 - Jira does not have such a problem
 - Even an user stuck on login screen, other users can use other Confluence features
 - When I undo <Connector> section at Confluence server.xml to original, the problem is solved.
    - This indicates Connector might be a problem
- Undoing httpd.conf (= not using mod_proxy) will not fix the problem

 

Would you help me to fix this problem?

 

Catalina Log:

WARN [ContainerBackgroundProcessor[StandardEngine[Standalone]]] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadDetected Thread [http-nio-8090-exec-19] (id=[242]) has been active for [62,930] milliseconds (since [18/12/25 9:26]) to serve the same request for [http://my.company.com/rest/usermanagement/1/authentication?username=Confluence+-+(IP)+-+b27ccadf-eb19-3763-b737-dd40e1c4ed72] and may be stuck (configured threshold for this StuckThreadDetectionValve is [60] seconds). There is/are [36] thread(s) in total that are monitored by this Valve and may be stuck.
java.lang.Throwable

  Full warning message is here: https://pastebin.com/vUKWT0t8

 

JIRA Connector (server.xml) (Working perfect):

 <Connector port="8080" relaxedPathChars="[]|" relaxedQueryChars="[]|{}^&#x5c;&#x60;&quot;&lt;&gt;"
maxThreads="150" minSpareThreads="25" connectionTimeout="20000" enableLookups="false"
maxHttpHeaderSize="8192" protocol="HTTP/1.1" useBodyEncodingForURI="true" redirectPort="8443"
acceptCount="100" disableUploadTimeout="true" bindOnInit="false" proxyName="my.company.com" proxyPort="80" scheme="http"/>

 

Confluence Original Connector (server.xml) (Working perfect):

 <Connector port="8090" connectionTimeout="20000" redirectPort="8443"
maxThreads="48" minSpareThreads="10"
enableLookups="false" acceptCount="10" debug="0" URIEncoding="UTF-8"
protocol="org.apache.coyote.http11.Http11NioProtocol"/>

 

Confluence Connector when triggering the problem:

 <Connector port="8090" connectionTimeout="20000" redirectPort="8443"
maxThreads="48" minSpareThreads="10"
enableLookups="false" acceptCount="10" debug="0" URIEncoding="UTF-8"
protocol="org.apache.coyote.http11.Http11NioProtocol" proxyName="my.company.com" proxyPort="80" scheme="http"/>

 

 Virtual host section (httpd.conf)


<VirtualHost *:80>
ServerName my.company.com
RemoteIPHeader X-Forwarded-For

ProxyRequests Off

Timeout 2400
ProxyTimeout 2400
ProxyBadHeader Ignore

<Proxy *>
Require all granted
</Proxy>

ProxyPass /synchrony http://localhost:8091/synchrony
<Location /synchrony>
Require all granted
RewriteEngine on
RewriteCond %{HTTP:UPGRADE} ^WebSocket$ [NC]
RewriteCond %{HTTP:CONNECTION} Upgrade$ [NC]
RewriteRule .* ws://localhost:8091%{REQUEST_URI} [P]
</Location>

ProxyPass /track http://localhost:8080/track
ProxyPassReverse /track http://localhost:8080/track

ProxyPass / http://localhost:8090/
ProxyPassReverse / http://localhost:8090/
</VirtualHost>

 

1 answer

0 votes
Johannes Swart
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!
November 26, 2020

Hi I know this is from two years ago but did you ever find a solution for this.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events