Last updated Feb 20, 2024

Cannot start plugin

Symptom: "Cannot start plugin"

This is a WARNING not an ERROR in the log. The plugin will also be shown as Disabled on the Admin, Plugins screen.

Cause: the OSGI plugin does not know anything about a class used when the plugin is started up

Solution: correct any typos in the interface attribute in the component-import element. Also make sure that the component is exported from elsewhere with a <component> element.


2010-02-24 16:18:52,882 main WARN     [plugin.osgi.factory.OsgiPlugin] Unable to enable plugin 'com.example.jira.plugins.example-errors'
com.atlassian.plugin.osgi.container.OsgiContainerException: Cannot start plugin: com.example.jira.plugins.example-errors
    at com.atlassian.plugin.osgi.factory.OsgiPlugin.enableInternal(

Note that the error messages do not show the name of the component that the OSGI container failed to import. In this case the problem was

<component-import key="foo" interface="com.example.does.not.exist"/>

Rate this page: