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

Jira 4.0 won't work with IBM JAVA 1.6

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • High
    • None
    • 4.0.1, 4.0.2, 4.1
    • None
    • JRE 1.6.0 IBM J9 2.4 AIX ppc64-64 jvmap6460sr6-20090923_42924
      JRE 1.6.0 IBM J9 2.4 Linux x86-32 jvmxi3260-20080816_22093

    Description

      Following error was thrown while runing JIRA 4.0.x with JRE 1.6.0 IBM J9 2.4:

      2010-03-15 15:26:52,343 main FATAL     [atlassian.jira.upgrade.ConsistencyLauncher] A fatal error occured during initialisation. JIRA has been locked.
      com.atlassian.jira.InfrastructureException: Error occurred while starting Plugin Manager. The plugin key 'com.atlassian.auiplugin' must either match the OSGi bundle symbolic name (Bundle-SymbolicName) or be specified in the Atlassian-Plugin-Key manifest header
      	at com.atlassian.jira.ComponentManager$PluginSystem.start(ComponentManager.java:1285)
      	at com.atlassian.jira.ComponentManager.quickStart(ComponentManager.java:224)
      	at com.atlassian.jira.ComponentManager.start(ComponentManager.java:210)
      	at com.atlassian.jira.upgrade.ConsistencyLauncher.launchConsistencyChecker(ConsistencyLauncher.java:63)
      	at com.atlassian.jira.upgrade.ConsistencyLauncher.contextInitialized(ConsistencyLauncher.java:42)
      	at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3934)
      	at org.apache.catalina.core.StandardContext.start(StandardContext.java:4429)
      	at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
      	at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
      	at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526)
      	at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:630)
      	at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:556)
      	at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:491)
      	at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1206)
      	at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:314)
      	at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
      	at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
      	at org.apache.catalina.core.StandardHost.start(StandardHost.java:722)
      	at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
      	at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
      	at org.apache.catalina.core.StandardService.start(StandardService.java:516)
      	at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
      	at org.apache.catalina.startup.Catalina.start(Catalina.java:583)
      	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
      	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
      	at java.lang.reflect.Method.invoke(Method.java:600)
      	at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
      	at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
      Caused by: java.lang.IllegalArgumentException: The plugin key 'com.atlassian.auiplugin' must either match the OSGi bundle symbolic name (Bundle-SymbolicName) or be specified in the Atlassian-Plugin-Key manifest header
      	at com.atlassian.plugin.osgi.factory.OsgiPluginUninstalledHelper.install(OsgiPluginUninstalledHelper.java:70)
      	at com.atlassian.plugin.osgi.factory.OsgiPlugin.installInternal(OsgiPlugin.java:316)
      	at com.atlassian.plugin.impl.AbstractPlugin.install(AbstractPlugin.java:299)
      	at com.atlassian.plugin.impl.AbstractDelegatingPlugin.install(AbstractDelegatingPlugin.java:203)
      	at com.atlassian.plugin.manager.DefaultPluginManager.addPlugins(DefaultPluginManager.java:537)
      	at com.atlassian.plugin.manager.DefaultPluginManager.init(DefaultPluginManager.java:152)
      	at com.atlassian.jira.plugin.JiraPluginManager.start(JiraPluginManager.java:49)
      	at com.atlassian.jira.ComponentManager$PluginSystem.start(ComponentManager.java:1275)
      	... 28 more
      2010-03-15 15:26:52,349 main FATAL     [atlassian.jira.upgrade.UpgradeLauncher] Skipping, JIRA is locked.
      2010-03-15 15:26:52,350 main INFO     [atlassian.jira.scheduler.JiraSchedulerLauncher] Starting the JIRA Scheduler....
      2010-03-15 15:26:52,350 main INFO     [atlassian.jira.scheduler.JiraSchedulerLauncher] Skipping JIRA Scheduler initialisation, JIRA is not ready.
      

      A similar issue was reported before: http://jira.atlassian.com/browse/JRA-19401 where the problem only happened on Websphere 7.0 and was resolved as "Won't Fix".

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              lding Lei Ding [Atlassian]
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: