-
Bug
-
Resolution: Tracked Elsewhere
-
Low (View bug fix roadmap)
-
None
-
6.1
-
None
-
6.01
-
When uninstalling plugins, database is not cleaned up correctly
There are different issues like
2014-02-25 08:28:51,607 ajp-bio-8009-exec-7 WARN MarcelSilberhorn 508x42x1 13apjq4 172.18.57.71 /rest/plugins/1.0/notifications [notification.rest.representations.NotificationRepresentationFactoryImpl] Notification exists for uninstalled and unrequested plugin: com.atlassian.bonfire.plugin
or
2013-10-08 12:41:35,886 localhost-startStop-1 ERROR [jira.issue.managers.DefaultCustomFieldManager] Could not load custom field type plugin with key 'com.atlassian.bonfire.plugin:bonfire-text'. Is the plugin present and enabled?
as an admin, I don't want to see such a mess in logs.
Also I'd be pleased to see some "cleanup" tasks in the backend.
- duplicates
-
-
- Closed
-
- is related to
-
-
- Closed
-
- was split into
-
UPM-4346 Clear error message upon clean-up of plugin requests for uninstalled plugins
- Done
[JRASERVER-37174] No Database Cleanup when uninstalling Plugins
As for the other log message about custom fields that's currently tracked at JRA-28134
Please feel free to add your thought and vote on that issue and watch it if you are interested in receiving updates about its status.
Regards,
Oswaldo Hernández.
JIRA Bugmaster.
[Atlassian].
Hi konqi,
For the first notification at:
2014-02-25 08:28:51,607 ajp-bio-8009-exec-7 WARN MarcelSilberhorn 508x42x1 13apjq4 172.18.57.71 /rest/plugins/1.0/notifications [notification.rest.representations.NotificationRepresentationFactoryImpl] Notification exists for uninstalled and unrequested plugin: com.atlassian.bonfire.plugin
From reviewing the source code, it seems like the notifications are indeed removed and then this message in printed to the logs. Perhaps the message could be changed so that this is more obvious? I have raised https://ecosystem.atlassian.net/browse/UPM-4346 to track this. Feel free to monitor that issue if you are interested in a fix for that.
From my understanding of the code this message should only happen once.
Dear ohernandez@atlassian.com , thank you for clarification, splitting and pointing out that dup.
Just one remark at UPM-4346: As far as I've seen this, the message appeared not only once but everytime on every startup .. but there was no error follow-up that a notification couldn't be removed or s.th. like that. Perhaps, error handling doesn't catch when s.th. going wrong? OR: there is also a second case where this message can be threw out?! Startup / shutdown cycle jira 10 times one after the other seems not to "clean" up.
another idea that might have confused me: are old logs displayed during startup?