After upgrade to 8.18.x version JIRA does not start

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

After an upgrade to the 8.18.x version of Jira, the JVM process starts up. But it is not listening on the configured port in server.xml and the login or dashboard page can't be loaded.

Environment

8.18.x

Diagnosis

Looking at the catalina.out file during the startup, we can see the protocol handler fail to start for connector on port 8080.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 13-Aug-2021 15:06:44.835 SEVERE [main] org.apache.catalina.core.StandardService.startInternal Failed to start connector [Connector[HTTP/1.1-8080]] org.apache.catalina.LifecycleException: Protocol handler start failed at org.apache.catalina.connector.Connector.startInternal(Connector.java:1101) ...... at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:766) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at org.apache.catalina.startup.Catalina.start(Catalina.java:688) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:342) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:473) Caused by: java.lang.IllegalArgumentException: Key protection algorithm not found: java.security.UnrecoverableKeyException: Encrypt Private Key failed: unrecognized algorithm name: PBEWithSHA1AndDESede

The server.xml shows that the port 8080 was configured to handle https traffic with keystore file location and other parameters provided.

Cause

Jira 8.18.x version uses JRE version 8u292. If instances are run with the default JRE packaged with Jira and the instance is configured to handle SSL connection at the Jira node itself rather than a proxy, users would encounter this problem due to https://bugs.openjdk.java.net/browse/JDK-8266261

Solution

1. Install a higher version of Jira such as 8.19. It contains a higher JRE version which avoids this problem.

2. Install AdoptopenJDK or Oracle JDK with a version higher than 292 and setting Jira to use the JDK.

Updated on March 10, 2025

Still need help?

The Atlassian Community is here for you.