Uploaded image for project: 'JIRA Labels Plugin'
  1. JIRA Labels Plugin
  2. LBL-195

JIRA won't start when using JIRA Labels and Java 1.6-21 or later

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 2.4
    • Fix Version/s: 2.3.1, 2.4.1
    • Component/s: Build
    • Security Level: public (Anyone can view the issue)
    • Labels:
    • Environment:

      JIRA 4.1.2
      Java 1.6u21,22,23
      JIRA Labels 2.4

      Description

      Hi,

      There is a critical bug that prevents JIRA to start when using JIRA Labels and the latest Java version.
      I made a test using a clean install, JIRA 4.1.2 and JIRA Labels 2.4.
      When using Java 1.6-21, JIRA hangs with a fatal error.

      2010-07-13 12:06:32,531 main ERROR      [plugin.event.impl.DefaultPluginEventManager] Plugin Event Listener 'com.atlassian.sal.jira.lifecycle.JiraLifecycleManager@15735fd' threw an error on event 'com.atlassian.jira.extension.JiraStartedEvent@1d92abb': org/picocontainer/PicoContainer
      2010-07-13 12:06:32,532 main FATAL      [atlassian.jira.upgrade.ConsistencyLauncher] A fatal error occured during initialisation. JIRA has been locked.
      com.atlassian.plugin.event.NotificationException: java.lang.NoClassDefFoundError: org/picocontainer/PicoContainer
      	at com.atlassian.plugin.event.impl.DefaultPluginEventManager.broadcast(DefaultPluginEventManager.java:85)
      	at com.atlassian.jira.ComponentManager.quickStart(ComponentManager.java:267)
      	at com.atlassian.jira.ComponentManager.start(ComponentManager.java:211)
      	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.start(ContainerBase.java:1045)
      	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:39)
      	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      	at java.lang.reflect.Method.invoke(Method.java:597)
      	at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
      	at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
      Caused by: java.lang.NoClassDefFoundError: org/picocontainer/PicoContainer
      	at com.atlassian.jira.plugin.labels.utils.BackwardsCompatibilitySupport.getOfBizDelegator(BackwardsCompatibilitySupport.java:95)
      	at com.atlassian.jira.plugin.labels.utils.BackwardsCompatibilitySupport.start(BackwardsCompatibilitySupport.java:37)
      	at com.atlassian.sal.jira.lifecycle.JiraLifecycleManager.notifyOnStart(JiraLifecycleManager.java:83)
      	at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager.start(DefaultLifecycleManager.java:50)
      	at com.atlassian.sal.jira.lifecycle.JiraLifecycleManager.onJiraStart(JiraLifecycleManager.java:60)
      	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      	at java.lang.reflect.Method.invoke(Method.java:597)
      	at com.atlassian.plugin.event.impl.DefaultPluginEventManager$Listener.notify(DefaultPluginEventManager.java:196)
      	at com.atlassian.plugin.event.impl.DefaultPluginEventManager.broadcast(DefaultPluginEventManager.java:70)
      	... 19 more
      Caused by: java.lang.ClassNotFoundException: org.picocontainer.PicoContainer
      	at org.apache.felix.framework.ModuleImpl.findClassOrResourceByDelegation(ModuleImpl.java:726)
      	at org.apache.felix.framework.ModuleImpl.access$100(ModuleImpl.java:60)
      	at org.apache.felix.framework.ModuleImpl$ModuleClassLoader.loadClass(ModuleImpl.java:1633)
      	at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
      	... 30 more
      2010-07-13 12:06:32,534 main FATAL      [atlassian.jira.upgrade.UpgradeLauncher] Skipping, JIRA is locked.
      
      

      When using Java 1.6-20, JIRA works perfectly!

      Cheers,
      Thiago Auler

        Gliffy Diagrams

          Attachments

            Activity

            Hide
            jcooi Joachim Ooi added a comment - - edited

            Here is the current workaround. Do either one of the below:

            • Downgrade your Java version to Update 20 and below.
            • Remove the plugin and upgrade to JIRA 4.2 - the labels functionality is built into 4.2 and it does not seem to have this problem.
            Show
            jcooi Joachim Ooi added a comment - - edited Here is the current workaround. Do either one of the below: Downgrade your Java version to Update 20 and below . Remove the plugin and upgrade to JIRA 4.2 - the labels functionality is built into 4.2 and it does not seem to have this problem.
            Hide
            dchui David Chui (Inactive) added a comment -

            We've implemented a fix for this issue in version 2.4.1 of this plugin. For those affected (running JIRA 4.1 with a newer JDK/Java), please upgrade the plugin to version 2.4.1. Do remember to remove the older version of the plugin.

            The fix we've implemented removes the dependency on Pico (which seemed to be the problem). Please let us know if there are still problems.

            Show
            dchui David Chui (Inactive) added a comment - We've implemented a fix for this issue in version 2.4.1 of this plugin. For those affected (running JIRA 4.1 with a newer JDK/Java), please upgrade the plugin to version 2.4.1. Do remember to remove the older version of the plugin. The fix we've implemented removes the dependency on Pico (which seemed to be the problem). Please let us know if there are still problems.
            Hide
            gbrauer1 Gregory Brauer added a comment -

            Will this fix be made available for a version of the plugin that works with JIRA 4.0.2?

            Show
            gbrauer1 Gregory Brauer added a comment - Will this fix be made available for a version of the plugin that works with JIRA 4.0.2?
            Hide
            dchui David Chui (Inactive) added a comment -

            Hi Gregory,

            Yes, I'll try to port the fix to 2.3

            Show
            dchui David Chui (Inactive) added a comment - Hi Gregory, Yes, I'll try to port the fix to 2.3
            Hide
            jalbion Janet Albion added a comment -

            This also affecting:

            • JIRA 4.0.2 with JIRA Label 2.3
            • JDK 1.5.0_28
            • OS X 10.5.8

            Upgrade to JIRA Label 2.3.1 fix the problem

            Show
            jalbion Janet Albion added a comment - This also affecting: JIRA 4.0.2 with JIRA Label 2.3 JDK 1.5.0_28 OS X 10.5.8 Upgrade to JIRA Label 2.3.1 fix the problem

              People

              • Assignee:
                dchui David Chui (Inactive)
                Reporter:
                tsantos Thiago Auler dos Santos
              • Votes:
                49 Vote for this issue
                Watchers:
                45 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Who's Looking?