JIRA throws exception 'Could not initialize class javax.crypto.SunJCE_b'

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

Symptoms

  1. $BASE_URL/secure/* does not works

The following appears in the atlassian-jira.log:

1 2012-06-21 08:58:50,005 http-xxx-3 ERROR admin 538x36x1 174e5bk xxx /secure/ViewProfile.jspa [com.atlassian.velocity.DefaultVelocityManager] MethodInvocationException occurred getting message body from Velocity: java.lang.NoClassDefFoundError: Could not initialize class javax.crypto.SunJCE_b

Diagnosis

  1. $BASE_URL/secure/Dashboard.jspa does not work

  2. But $BASE_URL/browse/ISSUE_KEY works

Cause

There is problem loading the encryption libraries in the JVM.

Solution

Resolution

  1. Ensure that the following JAR files does exist in the JIRA's JRE or the JIRA_HOME's JRE:

  • JRE/lib/security/local_policy.jar

  • JRE/lib/security/US_export_policy.jar

Updated on April 2, 2025

Still need help?

The Atlassian Community is here for you.