Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-6913

Uninstalling Jira Service Desk leaves behind "com.atlassian.psmq" plugin, preventing successful reinstall

    XMLWordPrintable

Details

    Description

      Summary

      Jira Service Desk does not re-install properly after having uninstalled it from Jira before, due to the fact that the plugin "com.atlassian.psmq" that Service Desk relies on is not re-enabled during the re-installation.

      Steps to Reproduce

      1. Install Jira 8.9.1 with Service Desk 4.9.1
      2. Create a Service Desk project
      3. Uninstall the Service Desk application from the page ⚙ > Applications > Versions & Licenses
      4. Reinstall Service Desk from the page ⚙ > Applications > Versions & Licenses and wait for 5 minutes
      5. Open any Service Desk project configuration page

      Expected Results

      • Service Desk installs successfully
      • Service Desk specific configurations (Request Types, SLAs, Automation rules...) can be accessed from Service Desk projects

      Actual Results

      • Service Desk installation takes a long time (300 seconds waiting for add-on timeout) to finish
      • Apparently Service Desk installs without any errors
      • However, Service Desk functionalities do not work properly, because the Service Desk Desk specific configurations (Request Types, SLAs, Automation rules...) are completely missing from any Service Desk configuration page:
      • When running the following SQL query, we can see that the plugin com.atlassian.psmq is disabled:
        select * from pluginstate;
             pluginkey      | pluginenabled 
        --------------------+---------------
         com.atlassian.psmq | false
        
      • the following errors are thrown in the logs:
        2020-06-29 17:03:38,116+0200 Spring DM Context Creation Timer ERROR      [c.a.p.osgi.factory.OsgiPlugin] Plugin 'com.atlassian.servicedesk.internal-base-plugin' never resolved service '&QSessionFactory' with filter '(&(objectClass=com.atlassian.psmq.api.QSessionFactory)(objectClass=com.atlassian.psmq.api.QSessionFactory))'
        2020-06-29 17:03:38,117+0200 Spring DM Context Creation Timer ERROR      [c.a.p.osgi.factory.OsgiPlugin] Unable to start the plugin container for plugin 'com.atlassian.servicedesk.internal-base-plugin'
        org.springframework.context.ApplicationContextException: Application context initialization for 'com.atlassian.servicedesk.internal-base-plugin' has timed out waiting for (&(objectClass=com.atlassian.psmq.api.QSessionFactory)(objectClass=com.atlassian.psmq.api.QSessionFactory))
        	at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.timeout(DependencyWaiterApplicationContextExecutor.java:489)
        	at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.access$000(DependencyWaiterApplicationContextExecutor.java:54)
        	at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$WatchDogTask.run(DependencyWaiterApplicationContextExecutor.java:109)
        	at java.util.TimerThread.mainLoop(Timer.java:555)
        	at java.util.TimerThread.run(Timer.java:505)
        2020-06-29 17:03:38,307+0200 Spring DM Context Creation Timer ERROR      [o.e.g.b.e.internal.support.ExtenderConfiguration] Application context refresh failed (NonValidatingOsgiBundleXmlApplicationContext(bundle=com.atlassian.servicedesk.internal-base-plugin, config=osgibundle:/META-INF/spring/*.xml))
        org.springframework.context.ApplicationContextException: Application context initialization for 'com.atlassian.servicedesk.internal-base-plugin' has timed out waiting for (&(objectClass=com.atlassian.psmq.api.QSessionFactory)(objectClass=com.atlassian.psmq.api.QSessionFactory))
        	at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.timeout(DependencyWaiterApplicationContextExecutor.java:489)
        	at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.access$000(DependencyWaiterApplicationContextExecutor.java:54)
        	at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$WatchDogTask.run(DependencyWaiterApplicationContextExecutor.java:109)
        	at java.util.TimerThread.mainLoop(Timer.java:555)
        	at java.util.TimerThread.run(Timer.java:505)
        2020-06-29 17:03:38,308+0200 Spring DM Context Creation Timer ERROR      [o.e.g.b.e.i.dependencies.startup.DependencyWaiterApplicationContextExecutor] Unable to create application context for [com.atlassian.servicedesk.internal-base-plugin], unsatisfied dependencies: Dependency on [(&(objectClass=com.atlassian.psmq.api.QSessionFactory)(objectClass=com.atlassian.psmq.api.QSessionFactory))] (from bean [&QSessionFactory])
        org.springframework.context.ApplicationContextException: Application context initialization for 'com.atlassian.servicedesk.internal-base-plugin' has timed out waiting for (&(objectClass=com.atlassian.psmq.api.QSessionFactory)(objectClass=com.atlassian.psmq.api.QSessionFactory))
        	at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.timeout(DependencyWaiterApplicationContextExecutor.java:489)
        	at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.access$000(DependencyWaiterApplicationContextExecutor.java:54)
        	at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$WatchDogTask.run(DependencyWaiterApplicationContextExecutor.java:109)
        	at java.util.TimerThread.mainLoop(Timer.java:555)
        	at java.util.TimerThread.run(Timer.java:505)
        2020-06-29 17:03:38,308+0200 Spring DM Context Creation Timer WARN      [o.e.g.b.e.i.dependencies.startup.DependencyWaiterApplicationContextExecutor] Timeout occurred before finding service dependencies for [NonValidatingOsgiBundleXmlApplicationContext(bundle=com.atlassian.servicedesk.servicedesk-lingo-plugin, config=osgibundle:/META-INF/spring/*.xml)]
        2020-06-29 17:03:38,309+0200 Spring DM Context Creation Timer ERROR      [c.a.p.osgi.factory.OsgiPlugin] Plugin 'com.atlassian.servicedesk.servicedesk-lingo-plugin' never resolved service '&cacheFactoryManager' with filter '(&(objectClass=com.atlassian.servicedesk.plugins.base.internal.api.cache.CacheFactoryManager)(objectClass=com.atlassian.servicedesk.plugins.base.internal.api.cache.CacheFactoryManager))'
        2020-06-29 17:03:38,309+0200 Spring DM Context Creation Timer ERROR      [c.a.p.osgi.factory.OsgiPlugin] Unable to start the plugin container for plugin 'com.atlassian.servicedesk.servicedesk-lingo-plugin'
        org.springframework.context.ApplicationContextException: Application context initialization for 'com.atlassian.servicedesk.servicedesk-lingo-plugin' has timed out waiting for (&(objectClass=com.atlassian.servicedesk.plugins.base.internal.api.cache.CacheFactoryManager)(objectClass=com.atlassian.servicedesk.plugins.base.internal.api.cache.CacheFactoryManager))
        	at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.timeout(DependencyWaiterApplicationContextExecutor.java:489)
        	at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.access$000(DependencyWaiterApplicationContextExecutor.java:54)
        	at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$WatchDogTask.run(DependencyWaiterApplicationContextExecutor.java:109)
        	at java.util.TimerThread.mainLoop(Timer.java:555)
        	at java.util.TimerThread.run(Timer.java:505)
        2020-06-29 17:03:38,313+0200 Spring DM Context Creation Timer ERROR      [o.e.g.b.e.internal.support.ExtenderConfiguration] Application context refresh failed (NonValidatingOsgiBundleXmlApplicationContext(bundle=com.atlassian.servicedesk.servicedesk-lingo-plugin, config=osgibundle:/META-INF/spring/*.xml))
        org.springframework.context.ApplicationContextException: Application context initialization for 'com.atlassian.servicedesk.servicedesk-lingo-plugin' has timed out waiting for (&(objectClass=com.atlassian.servicedesk.plugins.base.internal.api.cache.CacheFactoryManager)(objectClass=com.atlassian.servicedesk.plugins.base.internal.api.cache.CacheFactoryManager))
        	at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.timeout(DependencyWaiterApplicationContextExecutor.java:489)
        	at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.access$000(DependencyWaiterApplicationContextExecutor.java:54)
        	at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$WatchDogTask.run(DependencyWaiterApplicationContextExecutor.java:109)
        	at java.util.TimerThread.mainLoop(Timer.java:555)
        	at java.util.TimerThread.run(Timer.java:505)
        

      Workaround

      1. Stop JIRA
      2. Run the following SQL query from the Jira Database:
        delete from pluginstate where pluginkey = 'com.atlassian.psmq';
      3. Restart JIRA

      Attachments

        1. reinstall.log
          883 kB
        2. Screenshot1.png
          Screenshot1.png
          181 kB
        3. Screenshot2.png
          Screenshot2.png
          275 kB
        4. Screenshot3.png
          Screenshot3.png
          300 kB
        5. uninstall.log
          28 kB

        Issue Links

          Activity

            People

              c8bcca445054 Benjamin Suess
              jrey Julien Rey
              Votes:
              4 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Backbone Issue Sync