Hello, during the course of some investigation with Atlassian Support we had discovered that JIRA was performing poorly due to being routed through a proxy. Atlassian Support had asked that we attempt to comment out some lines in our server.xml configuration file for "scheme", "proxyName", and "proxyPort" to test accessing JIRA directly (bypassing the proxy: https://confluence.atlassian.com/jirakb/how-to-bypass-a-proxy-and-ssl-to-test-network-connectivity-827328189.html )
It turned out that JIRA performed great after bypassing the proxy and after quite some time testing back and forth with the proxy configuration, it was clear that the slow-down and timeouts was coming from the proxy.
Here are the lines we are using
<Connector port="8080"
maxThreads="150"
minSpareThreads="25"
connectionTimeout="20000"
enableLookups="false"
maxHttpHeaderSize="8192"
protocol="HTTP/1.1"
useBodyEncodingForURI="true"
redirectPort="8443"
acceptCount="100"
disableUploadTimeout="true"
scheme="https"
proxyName="jira.redacted"
proxyPort="443"
/> And here is our haproxy config
frontend http-jira
bind *:44333 ssl crt /etc/ssl/haproxy/jira_xxx.pem no-sslv3 no-tlsv10 no-tlsv11
backend jira
balance roundrobin
option httpchk
server our-jira-server-1 our-jira-server-1.ourdomain.com:8080 check
would it have to do with the bind address being mismatched or is there something else we should include in the haproxy config?
Any help would be greatly appreciated.