-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
7.3.0, 7.4.0, 7.3.1, 7.3.2, 7.3.3, 7.3.4, 7.3.5, 7.3.6, 7.3.7, 7.3.8, 7.4.1, 7.4.2, 7.5.0, 7.4.3, 7.4.4, 7.5.1, 7.5.2, 7.5.3
-
7.03
-
18
-
Severity 3 - Minor
-
4
-
Steps to Reproduce:
- Navigate to JIRA Installation Folder > bin
- Run the config.bat/sh to use JIRA Configuration Tool.
- Change to "Web Server" tab.
- Change to Https protocol and fill in the required fields.
- Saved the configuration.
- Run JIRA.
Expected Result:
- JIRA will start and accessible through HTTPS connector.
Actual result:
- JIRA would not be able to start due to the HTTPS connector with error:
07-Feb-2017 13:23:12.795 SEVERE [main] org.apache.catalina.core.StandardService.initInternal Failed to initialize connector [Connector[org.apache.coyote.http11.Http11Protocol-443]] org.apache.catalina.LifecycleException: Failed to initialize component [Connector[org.apache.coyote.http11.Http11Protocol-443]] at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:112) at org.apache.catalina.core.StandardService.initInternal(StandardService.java:549) at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107) ...
Notes:
- The cause will be the protocol used is not org.apache.coyote.http11.Http11NioProtocol as mentioned in:
- The tool is still using org.apache.coyote.http11.Http11Protocol
- blocks
-
JRASERVER-63734 Tomcat fails to start in 7.3+ due to protocol deprecation in Tomcat 8.5
- Closed
- duplicates
-
JRASERVER-64082 Jira Configuration Tool sets wrong value of the 'protocol' attribute for Tomcat SSL configuration
- Closed
- mentioned in
-
Page Loading...