'java.lang.IllegalStateException: Bundle is uninstalled' Errors in JIRA log files too verbose

XMLWordPrintable

      The following error covered here often means that there's been a plugin startup failure or there's an incompatible plugin on the customers JIRA instance that's failed.

      Stack trace:

      2013-10-21 16:14:02,343 http-bio-8080-exec-30 ERROR anonymous 974x380982x8 4cg4eu 10.1.50.244 /rest/usermanagement/1/user/group/nested [atlassian.plugin.servlet.DefaultServletModuleManager] Unable to create filter
com.atlassian.util.concurrent.LazyReference$InitializationException: java.lang.IllegalStateException: Bundle is uninstalled
	at com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:149)
	at com.atlassian.util.concurrent.LazyReference.get(LazyReference.java:112)
	at com.atlassian.plugin.servlet.DefaultServletModuleManager.getFilter(DefaultServletModuleManager.java:389)
	at com.atlassian.plugin.servlet.DefaultServletModuleManager.getFilters(DefaultServletModuleManager.java:213)
	at com.atlassian.plugin.servlet.filter.ServletFilterModuleContainerFilter.doFilter(ServletFilterModuleContainerFilter.java:75)  <+34> (ServletFilterModuleContainerFilter.java:63) (ApplicationFilterChain.java:243) (ApplicationFilterChain.java:210) (ChainedFilterStepRunner.java:84) (ApplicationFilterChain.java:243) (ApplicationFilterChain.java:210) (AbstractCachingFilter.java:33) (AbstractHttpFilter.java:31) (ApplicationFilterChain.java:243) (ApplicationFilterChain.java:210) (AbstractEncodingFilter.java:41) (AbstractHttpFilter.java:31) (PathMatchingEncodingFilter.java:45) (AbstractHttpFilter.java:31) (ApplicationFilterChain.java:243) (ApplicationFilterChain.java:210) (JiraStartupChecklistFilter.java:74) (ApplicationFilterChain.java:243) (ApplicationFilterChain.java:210) (ChainedFilterStepRunner.java:84) (JiraFirstFilter.java:57) (ApplicationFilterChain.java:243) (ApplicationFilterChain.java:210) (StandardWrapperValve.java:225) (StandardContextValve.java:123) (AuthenticatorBase.java:472) (StandardHostValve.java:168) (ErrorReportValve.java:98) (StandardEngineValve.java:118) (AccessLogValve.java:927) (CoyoteAdapter.java:407) (AbstractHttp11Processor.java:1001) (AbstractProtocol.java:585) (JIoEndpoint.java:312)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.IllegalStateException: Bundle is uninstalled
	at org.apache.felix.framework.Felix.loadBundleClass(Felix.java:1574)
	at org.apache.felix.framework.BundleImpl.loadClass(BundleImpl.java:887)
	at com.atlassian.plugin.osgi.util.BundleClassLoaderAccessor.loadClass(BundleClassLoaderAccessor.java:46)
	at com.atlassian.plugin.osgi.factory.OsgiPluginInstalledHelper.loadClass(OsgiPluginInstalledHelper.java:63)
	at com.atlassian.plugin.osgi.factory.OsgiPlugin.loadClass(OsgiPlugin.java:204)
	at com.atlassian.plugin.module.ClassPrefixModuleFactory.createModule(ClassPrefixModuleFactory.java:27)
	at com.atlassian.plugin.module.PrefixDelegatingModuleFactory.createModule(PrefixDelegatingModuleFactory.java:100)
	at com.atlassian.plugin.servlet.descriptors.ServletFilterModuleDescriptor.getModule(ServletFilterModuleDescriptor.java:135)  <+1> (DelegatingPluginFilter.java:35)
	at com.atlassian.plugin.servlet.DefaultServletModuleManager$LazyLoadedFilterReference.create(DefaultServletModuleManager.java:441)
	at com.atlassian.plugin.servlet.DefaultServletModuleManager$LazyLoadedFilterReference.create(DefaultServletModuleManager.java:427)
	at com.atlassian.util.concurrent.LazyReference$Sync.run(LazyReference.java:321)
	at com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:143)
	... 41 more

      The danger here is that the above stacktrace fills the logs over and over again, in some cases flooding them so much disk space has become a concern for the customer.

      Two ideas to fix this:

      • Make the errors less verbose (only really needs to come up once per busted plugin)
      • Warn the admin user in the header what is happening (and possibly which plugin is causing it) so that they can fix this themselves not requiring support intervention (this may need to be a feature)

            Assignee:
            Unassigned
            Reporter:
            Michael Andreacchio
            Votes:
            1 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated:
              Resolved: