Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-64037

JIRA Configuration Tool did not use the right protocol for SSL

    XMLWordPrintable

Details

    • 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

    Description

      Steps to Reproduce:

      1. Navigate to JIRA Installation Folder > bin
      2. Run the config.bat/sh to use JIRA Configuration Tool.
      3. Change to "Web Server" tab.
      4. Change to Https protocol and fill in the required fields.
      5. Saved the configuration.
      6. 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

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              jrahmadiputra Julian (Inactive)
              Votes:
              5 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: