We have upgraded JIRADC from7.6.2 to 7.13 .
- Initially we faced this issues ("2018-12-26 10:55:53,359 localhost-startStop-1 ERROR [c.a.jira.health.HealthChecks] Tomcat is misconfigured
2018-12-26 10:55:53,359 localhost-startStop-1 ERROR [c.a.jira.health.HealthChecks] The server.xml file is missing parameters needed by Jira to handle requests that contain special characters.") . fixed using the atlasian fix FIX-server.xml-to-handle special-characrters. After that individual nodes and individual fallback urls are working fine on port no.8080 and 8443. - But the problem is F5 load balancer which was working fine with 7.6.2 version is not resolving the health check with port 8443 , though 8080 health check is fine at F5 LB with version 7.13 .
- Health checks for individual nodes https://nl001572.tst.kohls.com:8443/ , https://nl001572.tst.kohls.com:8443/status are giving the output {"state":"RUNNING"} . But at F5 only for port 8080 health check is resolving , for 8443 it is not resolving .
- server.xml connector block is below.
<Service name="Catalina">
<Connector port="8080" relaxedPathChars="[]|" relaxedQueryChars="[]|{}^\`"<>"
maxThreads="150"
minSpareThreads="25"
connectionTimeout="20000"
enableLookups="false"
maxHttpHeaderSize="8192"
protocol="HTTP/1.1"
useBodyEncodingForURI="true"
redirectPort="8443"
acceptCount="100"
disableUploadTimeout="true"
bindOnInit="false"/>
<Connector port="8443" relaxedPathChars="[]|" relaxedQueryChars="[]|{}^\`"<>" maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25"
protocol="org.apache.coyote.http11.Http11NioProtocol"
enableLookups="false" disableUploadTimeout="true"
acceptCount="100" scheme="https" secure="true"
clientAuth="false" sslProtocols="TLSv1.2" sslEnabledProtocols="TLSv1.2" SSLEnabled="true"
URIEncoding="UTF-8" keystorePass="4jA1c/Ajvqs8" keystoreFile="/kohls/apps/app/jira/jiradc-tst.kohls.com.jks"/>
- please help on this on top priority .