[JRASERVER-64082] Jira Configuration Tool sets wrong value of the 'protocol' attribute for Tomcat SSL configuration

Type: Bug
Resolution: Fixed
Priority: Medium (View bug fix roadmap)
Fix Version/s: 7.7.0, 7.6.3
Affects Version/s: 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.4.3, 7.4.4
Component/s: System Administration - Configuration Tool
Labels:
- affects-server

Fixed in Long Term Support Release/s:

Download 7.6
Introduced in Version:
7.03
Support reference count:
57
Symptom Severity:
Severity 2 - Major
UIS:
43
Bug Fix Policy:
View Atlassian Server bug fix policy

Steps to Reproduce

Trigger JIRA Configuration Tool
Got to "Web Server" tab
Setup "Profile" to use HTTPS
Save changes.
Start JIRA.

Expected Results

JIRA starts with SSL enabled

Actual Results

Tomcat fails and is unable to start. The below exception is thrown in the catalina.out file:

06-Jan-2017 11:46:26.846 SEVERE [main] org.apache.catalina.connector.Connector.<init> Protocol handler instantiation failed
 java.lang.ClassNotFoundException: org.apache.coyote.http11.Http11Protocol
	at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
	at java.lang.Class.forName0(Native Method)
	at java.lang.Class.forName(Class.java:264)
	at org.apache.catalina.connector.Connector.<init>(Connector.java:74)
	at org.apache.catalina.startup.ConnectorCreateRule.begin(ConnectorCreateRule.java:64)
	at org.apache.tomcat.util.digester.Digester.startElement(Digester.java:1190)
	at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:509)
	at com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:182)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:1339)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2784)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:602)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:505)
	at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:841)
	at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:770)
	at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
	at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213)
	at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:643)
	at org.apache.tomcat.util.digester.Digester.parse(Digester.java:1458)
	at org.apache.catalina.startup.Catalina.load(Catalina.java:578)
	at org.apache.catalina.startup.Catalina.load(Catalina.java:629)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:311)
	at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:494)

Workaround

Modify JIRA_INSTALL/conf/server.xml. Change the protocol on your HTTPS connector to: protocol="org.apache.coyote.http11.Http11NioProtocol"

If you do not use the HTTP Connector but use the AJP Connector instead, use the AJP NIO protocol instead.
- The AJP connector is: protocol="org.apache.coyote.ajp.AjpNioProtocol"

Refer to Upgrade notes for 7.3 for instructions. See Running JIRA applications over SSL.

See Running JIRA applications over SSL or HTTPS for full directions on running JIRA over SSL or HTTPS.

is duplicated by

JRASERVER-64037 JIRA Configuration Tool did not use the right protocol for SSL

Closed

is related to

JRASERVER-63734 Tomcat fails to start in 7.3+ due to protocol deprecation in Tomcat 8.5

Closed

mentioned in: Page No Confluence page found with the given URL.; Page No Confluence page found with the given URL.; Running JIRA applications over SSL or HTTPS; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...

relates to: RAID-670 Loading...

was cloned as: RAID-345 Loading...

(12 mentioned in, 1 relates to, 1 was cloned as)

Pawel Farid (Inactive) added a comment - 23/Nov/2017 11:48 AM

Hi,

Sorry to hear that you have encountered this bug as well. We are working on providing a fix in the Jira Config Tool in order to provide a long term solution for this problem. However this specific bug has not been given our high or highest priority because there does exist a work-around for this problem. We know other users are going to encounter this issue, but we have tried to mitigate this by creating upgrade notes in the 7.3 documentation to highlight this problem and how to fix it: https://confluence.atlassian.com/display/JIRASOFTWARE/JIRA+Software+7.3.x+upgrade+notes. Moving forward we are interested to fix this bug to both help our end users and reduce the number of support cases caused by this problem. We are planning to have it fixed in 7.6.X. As soon we have a specific version locked down I will let you know. Our bug fix policy does explain in more depth how we approach fixing bugs in our products, https://confluence.atlassian.com/support/atlassian-bug-fixing-policy-201294573.html

Regards,

Pawel Farid

Jira Dev Manager

Pawel Farid (Inactive) added a comment - 23/Nov/2017 11:48 AM Hi, Sorry to hear that you have encountered this bug as well. We are working on providing a fix in the Jira Config Tool in order to provide a long term solution for this problem. However this specific bug has not been given our high or highest priority because there does exist a work-around for this problem. We know other users are going to encounter this issue, but we have tried to mitigate this by creating upgrade notes in the 7.3 documentation to highlight this problem and how to fix it: https://confluence.atlassian.com/display/JIRASOFTWARE/JIRA+Software+7.3.x+upgrade+notes . Moving forward we are interested to fix this bug to both help our end users and reduce the number of support cases caused by this problem. We are planning to have it fixed in 7.6.X. As soon we have a specific version locked down I will let you know. Our bug fix policy does explain in more depth how we approach fixing bugs in our products, https://confluence.atlassian.com/support/atlassian-bug-fixing-policy-201294573.html Regards, Pawel Farid Jira Dev Manager

Chris Wilhelm added a comment - 12/Aug/2017 1:06 AM

Just ran into this today helping a co-worker.

Basically, after running the config.bat (windows installation) and setting the https "stuff", starting the JIRA service failed. Put back the original server.xml, and it works. Figure out the difference and look in the log files.

Saw error message as noted above. Did google search for "jira java.lang.ClassNotFoundException: org.apache.coyote.http11.Http11Protocol" Took me straight here.

Problem fixed; but yeah, might want to fix what is generated by the jira-configurator.jar

Chris Wilhelm added a comment - 12/Aug/2017 1:06 AM Just ran into this today helping a co-worker. Basically, after running the config.bat (windows installation) and setting the https "stuff", starting the JIRA service failed. Put back the original server.xml, and it works. Figure out the difference and look in the log files. Saw error message as noted above. Did google search for "jira java.lang.ClassNotFoundException: org.apache.coyote.http11.Http11Protocol" Took me straight here. Problem fixed; but yeah, might want to fix what is generated by the jira-configurator.jar

IT Department added a comment - 25/Jul/2017 9:22 AM

How is this still a bug since February? As William mentioned above, a fresh out of the box install with SSL enabled doesn't work. That should be a major flaw needing to be prioritized considering this workaround isn't exactly easy to find.

It also means we have to do this manual work around every time we do an upgrade.

IT Department added a comment - 25/Jul/2017 9:22 AM How is this still a bug since February? As William mentioned above, a fresh out of the box install with SSL enabled doesn't work. That should be a major flaw needing to be prioritized considering this workaround isn't exactly easy to find. It also means we have to do this manual work around every time we do an upgrade.

William Clark added a comment - 25/May/2017 3:54 PM - edited

Why is this NOT set to high priority? The automated windows install WILL NOT WORK as currently sold without manual configuration that is no where to be found in the documentation.

William Clark added a comment - 25/May/2017 3:54 PM - edited Why is this NOT set to high priority? The automated windows install WILL NOT WORK as currently sold without manual configuration that is no where to be found in the documentation.

Jira Data Center

Details

Description

Steps to Reproduce

Expected Results

Actual Results

Workaround

Attachments

Issue Links

Forms

Activity

Collapse comment: Pawel Farid (Inactive) added a comment - 23/Nov/2017 11:48 AM

Expand comment: Pawel Farid (Inactive) added a comment - 23/Nov/2017 11:48 AM

Collapse comment: Chris Wilhelm added a comment - 12/Aug/2017 1:06 AM

Expand comment: Chris Wilhelm added a comment - 12/Aug/2017 1:06 AM

Collapse comment: IT Department added a comment - 25/Jul/2017 9:22 AM

Expand comment: IT Department added a comment - 25/Jul/2017 9:22 AM

Collapse comment: William Clark added a comment - 25/May/2017 3:54 PM, Edited by William Clark - 25/May/2017 3:55 PM

Expand comment: William Clark added a comment - 25/May/2017 3:54 PM, Edited by William Clark - 25/May/2017 3:55 PM

People

Dates