JIRA Upgrade or Startup failed due to UnsupportedOperationException

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

Symptoms

While upgrading JIRA and using JAVA 7, the following appears in the atlassian-jira.log:

1 2 3 4 5 6 7 8 9 10 2013-08-02 14:42:34,319 localhost-startStop-1 WARN [factory.transform.stage.ScanDescriptorForHostClassesStage] The plugin 'jira-gadgets-plugin-6.0.5.jar' uses a package 'com.atlassian.jira.dashboard' that is also exported by the application. It is highly recommended that the plugin use its own packages. 2013-08-02 14:42:39,119 localhost-startStop-1 ERROR [atlassian.plugin.loaders.ScanningPluginLoader] Unable to deploy plugin 'org.objectweb.asm-3.3.1.v201105211655' from 'Unit: /usr/local/jira-home/plugins/.bundled-plugins/org.objectweb.asm-3.3.1.v201105211655.jar (1374564542000)'. 2013-08-02 14:42:39,120 localhost-startStop-1 ERROR [atlassian.plugin.loaders.ScanningPluginLoader] Because of the following exception: java.lang.UnsupportedOperationException at java.util.AbstractMap$SimpleImmutableEntry.setValue(AbstractMap.java:759) at org.apache.felix.framework.BundleImpl.getCurrentLocalizedHeader(BundleImpl.java:442) at org.apache.felix.framework.Felix.getBundleHeaders(Felix.java:1404) at org.apache.felix.framework.BundleImpl.getHeaders(BundleImpl.java:312) at org.apache.felix.framework.BundleImpl.getHeaders(BundleImpl.java:294) ...

Cause

It's a bug with Felix framework, the argument -XX:+AggressiveOpts doesn't working with JAVA version 7.

Resolution

  1. Shutdown JIRA;

  2. Remove the argument -XX:+AggressiveOpts from the start up options;

  3. Restart JIRA;

Updated on April 7, 2025

Still need help?

The Atlassian Community is here for you.