NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.

      Summary

      Enabling and installing Service Desk in a certain way is causing it to fail. We believe it is something to do with:

      1. Installing via the UPM and it semi fails - the plugin is disabled.
      2. The license is entered, and the UPM accepts it.
      3. The plugin is enabled and a different error message is generated.

      Steps to Reproduce

      Install Service Desk in the specific order that makes it not work, which is still to be discovered.

      Expected Results

      Service Desk enables successfully.

      Actual Results

      The following stack trace is thrown:

      2013-10-02 19:21:16,226 ThreadPoolAsyncTaskExecutor::Thread 28 ERROR tcarter 1343x33956x1 n05ov1 99.110.160.171 /rest/plugins/1.0/available/popular [extender.internal.activator.ContextLoaderListener] Application context refresh failed (NonValidatingOsgiBundleXmlApplicationContext(bundle=com.atlassian.servicedesk, config=osgibundle:/META-INF/spring/*.xml))
      org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected exception parsing XML document from URL [bundle://142.0:0/META-INF/spring/spring.xml]; nested exception is java.lang.IllegalStateException: Invalid BundleContext.
      	at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:420)
      	at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:342)
      	at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:310)
      	at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:143)
      	at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:178)
      	at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:149)
      	at org.springframework.osgi.context.support.OsgiBundleXmlApplicationContext.loadBeanDefinitions(OsgiBundleXmlApplicationContext.java:164)
      	at org.springframework.osgi.context.support.OsgiBundleXmlApplicationContext.loadBeanDefinitions(OsgiBundleXmlApplicationContext.java:136)
      	at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:123)
      	at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:422)
      	...
      Caused by: java.lang.IllegalStateException: Invalid BundleContext.
      	at org.apache.felix.framework.BundleContextImpl.checkValidity(BundleContextImpl.java:365)
      	at org.apache.felix.framework.BundleContextImpl.getServiceReference(BundleContextImpl.java:256)
      	at org.springframework.osgi.io.internal.resolver.PackageAdminResolver$1.run(PackageAdminResolver.java:178)
      	at java.security.AccessController.doPrivileged(Native Method)
      

      Workaround

      Increase the plugin start timeout from default 60 seconds to 300 seconds by specifying the startup parameter -Datlassian.plugins.enable.wait=300. For a better description please see Resolution #4 on following page: https://confluence.atlassian.com/display/JIRAKB/JIRA+System+Plugin+Timeout+While+Waiting+for+Plugins+to+Enable

      Restarting JIRA without specifying this parameter has been known to workaround the problem. Please note though that if you don't specify the increased timeout you will likely run into the same problem when you try updating the plugin to a newer version in UPM.

            [JSDSERVER-2] Service Desk fails to enable due to Invalid BundleContext

            Thanks for your response! The reason I asked was because I got a similar (but maybe not quite the same) error yesterday in support.a.c (in our development environment), where I was not able to enable the JSD plugin and saw similar "Unexpected exception parsing XML document from URL" messages in the logs. I fixed it by restarting JIRA, and I was mainly curious if this was a relatively new fix, and, if so, if we would need to upgrade JSD to pick it up. However, if it's been released for a while, then I'm sure we are fine. As for my issue, I'll just keep an eye out to see if it happens again, and I'll raise an issue with more details if so.

            Ben Porter [Administrative account] added a comment - - edited Thanks for your response! The reason I asked was because I got a similar (but maybe not quite the same) error yesterday in support.a.c (in our development environment), where I was not able to enable the JSD plugin and saw similar "Unexpected exception parsing XML document from URL" messages in the logs. I fixed it by restarting JIRA, and I was mainly curious if this was a relatively new fix, and, if so, if we would need to upgrade JSD to pick it up. However, if it's been released for a while, then I'm sure we are fine. As for my issue, I'll just keep an eye out to see if it happens again, and I'll raise an issue with more details if so.

            bporter+admin,

            This issues was fixed a long time ago. It involved a number of factors such that (sometimes) our startup code ran so slow that the plugin system "timed us out" and we where considered and invalid bundle (aka plugin)

            We have not experienced this problem for a very long time.

            ɹǝʞɐq pɐɹq added a comment - bporter+admin , This issues was fixed a long time ago. It involved a number of factors such that (sometimes) our startup code ran so slow that the plugin system "timed us out" and we where considered and invalid bundle (aka plugin) We have not experienced this problem for a very long time.

            Has this been released yet in an official JSD plugin version?

            Ben Porter [Administrative account] added a comment - Has this been released yet in an official JSD plugin version?

            Having the same issue on JIRA 6.1.1 Standalone with Service desk 1.0.4 on RedHat Enterprise Linux 6.4 with Mysql 5.5.33.
            Will try the workaround tonight.

            Emre Toptancı [OBSS] added a comment - Having the same issue on JIRA 6.1.1 Standalone with Service desk 1.0.4 on RedHat Enterprise Linux 6.4 with Mysql 5.5.33. Will try the workaround tonight.

            We have improved the startup time of Service Desk in version 1.0.3, which should help some of the timeout cases we've seen so far.

            However, we also believe there are more improvements to be made in that area, so I'm leaving this issue open until those improvements have been implemented.

            Gilmore Davidson (Inactive) added a comment - We have improved the startup time of Service Desk in version 1.0.3, which should help some of the timeout cases we've seen so far. However, we also believe there are more improvements to be made in that area, so I'm leaving this issue open until those improvements have been implemented.

              Unassigned Unassigned
              dcurrie@atlassian.com Dave C
              Affected customers:
              3 This affects my team
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: