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

Notify Admin users of Disabled/Incompatible plugins on startup on JIRA interface

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Won't Fix
    • None
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Support commonly sees this error in users logs 'java.lang.IllegalStateException: Bundle is uninstalled' Error Due to Incompatible Plugin

      2012-03-07 21:35:29,564 http-80-4 ERROR anonymous 1295x3x3 - 192.168.250.43 /plugins/servlet/streams [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:152)
      ...
      Caused by: java.lang.IllegalStateException: Bundle is uninstalled
          at org.apache.felix.framework.Felix.loadBundleClass(Felix.java:1574)
      

      This can be pretty confusing for admins as they may not notice anyting in their instance until something goes wrong, with the power of the UPM and knowing what plugins have started and are working it would be good to notify admin users in the header or admin panel of the dysfunctional plugins.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              mandreacchio Michael Andreacchio
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: