Errors in the Jira logs after upgrade from 4.0.x to 4.4.3

[Milind Shah]

Hello,

I upgraded from Jira 4.0 version to 4.4.3 and the upgrades seems to be successful and I can access the application.

When I start the app there are 3 errors in the logs

2011-10-29 00:35:16,261 main ERROR [jira.issue.managers.DefaultCustomFieldManager] Could not load custom field type plugin with key 'com.atlassian.jira.ext.charting:firstresponsedate'. Is the plugin present and enabled?

2011-10-29 00:35:16,446 main ERROR [jira.issue.managers.DefaultCustomFieldManager] Could not load custom field type plugin with key 'com.atlassian.jira.ext.charting:timeinstatus'. Is the plugin present and enabled?

2011-10-29 00:35:16,458 main ERROR [jira.issue.managers.DefaultCustomFieldManager] Could not load custom field type plugin with key 'com.burningcode.jira.issue.customfields.impl.jira-watcher-field:watcherfieldtype'. Is the plugin present and enabled?

I have installed latest version of the needed plugins using the Jira plugin manager:

-rw-rw-r-- 1 jira jira 18K Oct 28 23:28 plugin.6759154626977158298.jira-watcher-field-2.4.1.jar

-rw-rw-r-- 1 jira jira 200K Oct 28 23:38 plugin.5620384687387783633.jira-charting-plugin-1.7.1.jar

Please let me know if you know a fix.

[AlexH]

Are those plugins being loaded later in the startup sequence? After GreenHopper for example? GreenHopper does something when it is loaded that causes the CustomFieldManager to try and load all customfields -- even though some plugins that provide the customfield logic necessary may not have loaded yet.

There should be an entry in the log for each plugin being loaded, see if those plugins are being loaded later in the startup sequence.

[Milind Shah]

I think you might be correct. These errors occur after greenhopper tries to load and later in the logs I see that these plugins have been loaded.

main INFO [atlassian.plugin.util.WaitUntil] Plugins that have yet to be enabled: [com.pyxis.greenhopper.jira], 55 seconds remaining

main ERROR [jira.issue.managers.DefaultCustomFieldManager] Could not load custom field type plugin with key 'com.atlassian.jira.ext.charting:firstresponsedate'. Is the plugin present and enabled?

main ERROR [jira.issue.managers.DefaultCustomFieldManager] Could not load custom field type plugin with key 'com.atlassian.jira.ext.charting:timeinstatus'. Is the plugin present and enabled?

main ERROR [jira.issue.managers.DefaultCustomFieldManager] Could not load custom field type plugin with key 'com.burningcode.jira.issue.customfields.impl.jira-watcher-field:watcherfieldtype'. Is the plugin present and enabled?

main INFO [atlassian.plugin.loaders.ScanningPluginLoader] Plugin Unit: .../jira-charting-plugin-1.7.1.jar created

main INFO [atlassian.plugin.loaders.ScanningPluginLoader] Plugin Unit: .../jira-watcher-field-2.4.1.jar created

JIRA Charting Plugin : com.atlassian.jira.ext.charting

Version : 1.7.1

Status : enabled

Vendor : Atlassian

Description : JIRA Plugin for graphical charts and graphs.

JIRA Watcher Field : com.burningcode.jira.issue.customfields.impl.jira-watcher-field

Version : 2.4.1

Status : enabled

Vendor : (unknown)

Description : Custom field type that allows watchers to be modified on the creation and update of issue.

[AlexH]

As far as I can tell the errors are harmless and simply a result of the loading process, because once the plugin loads a few seconds later all the functionality provided by that plugin works fine.

That said this is all new to me as well, so if someone else wants to confirm this is normal/allowed/expected behavior that'd be great.

[Nic Brough -Adaptavist-]

Check first that the plugins are enabled - sometimes they are disabled by something, especially when you've made structural changes like upgrades.

If they aren't, try enabling them and check what the response is - if it works, great, if not, then the screen might tell you why, and even if the screen doesn't, the log almost certainly will. If that doesn't help, or they don't appear there at all, have a look at the logs around startup time - if the plugins are installed, Jira will try to load them and if they fail to load or load and disable themselves, the reason will be in the logs.

[Jobin Kuruvilla [Adaptavist]]

Either the custom field types are discontinued or the plugin key got changed. You will be able to find it out from the atlassian-plugin.xml