-
Bug
-
Resolution: Fixed
-
Medium
-
5.8.18, 5.9.4, 5.9.9, 5.10.6, 5.10.8, 6.0.1, 6.0.3
-
None
-
28
-
Severity 2 - Major
-
Summary
Confluence will attempt to start plugin which have dependency on another plugin which has been disable. The confluence should disable the plugin which it has dependency on another plugin that has been disable
Step to reproduce:
- Disable the following plugin
- Atlassian Hipchat Integration Plugin
- Atlassian Hipchat Integration Plugin Core
- The following plugin which it has depency on the plugins above will be shown as disable in the manage add ons page
- Confluence Hipchat Emoticons Plugin
- Confluence Hipchat Integration Plugin
- Restart Confluence
Expected result, all the plugin related
The Confluence will not attempt to start the hipchat plugin
Observed Result
The Confluence is still trying to start the hipchat plugin which suppose to be disabled. This will slowdown the startup as it will attempt to start the plugin before timeout.
'com.atlassian.confluence.plugins.confluence-hipchat-emoticons-plugin' never resolved service '&hipChatLinkProvider' with filter '(objectClass=com.atlassian.plugins.hipchat.api.link.HipChatLinkProvider)' 2016-01-13 10:08:25,552 ERROR [Spring DM Context Creation Timer] [plugin.osgi.factory.OsgiPlugin] onPluginContainerFailed Unable to start the plugin container for plugin 'com.atlassian.confluence.plugins.confluence-hipchat-emoticons-plugin' org.springframework.context.ApplicationContextException: Application context initialization for 'com.atlassian.confluence.plugins.confluence-hipchat-emoticons-plugin' has timed out waiting for (objectClass=com.atlassian.plugins.hipchat.api.link.HipChatLinkProvider) at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.timeout(DependencyWaiterApplicationContextExecutor.java:489) at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.access$000(DependencyWaiterApplicationContextExecutor.java:54) at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$WatchDogTask.run(DependencyWaiterApplicationContextExecutor.java:109) at java.util.TimerThread.mainLoop(Timer.java:555) at java.util.TimerThread.run(Timer.java:505) 2016-01-13 10:08:25,603 ERROR [Spring DM Context Creation Timer] [extender.internal.support.ExtenderConfiguration] onOsgiApplicationEvent Application context refresh failed (NonValidatingOsgiBundleXmlApplicationContext(bundle=com.atlassian.confluence.plugins.confluence-hipchat-emoticons-plugin, config=osgibundle:/META-INF/spring/*.xml)) org.springframework.context.ApplicationContextException: Application context initialization for 'com.atlassian.confluence.plugins.confluence-hipchat-emoticons-plugin' has timed out waiting for (objectClass=com.atlassian.plugins.hipchat.api.link.HipChatLinkProvider) at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.timeout(DependencyWaiterApplicationContextExecutor.java:489) at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.access$000(DependencyWaiterApplicationContextExecutor.java:54) at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$WatchDogTask.run(DependencyWaiterApplicationContextExecutor.java:109) at java.util.TimerThread.mainLoop(Timer.java:555) at java.util.TimerThread.run(Timer.java:505) 2016-01-13 10:08:25,606 ERROR [Spring DM Context Creation Timer] [internal.dependencies.startup.DependencyWaiterApplicationContextExecutor] fail Unable to create application context for [com.atlassian.confluence.plugins.confluence-hipchat-emoticons-plugin], unsatisfied dependencies: Dependency on [(objectClass=com.atlassian.plugins.hipchat.api.link.HipChatLinkProvider)] (from bean [&hipChatLinkProvider]) org.springframework.context.ApplicationContextException: Application context initialization for 'com.atlassian.confluence.plugins.confluence-hipchat-emoticons-plugin' has timed out waiting for (objectClass=com.atlassian.plugins.hipchat.api.link.HipChatLinkProvider)
Workaround
Disable all the hipchat plugin in the following order:
- Confluence Hipchat Emoticons Plugin
- Confluence Hipchat Integration Plugin
- Atlassian Hipchat Integration Plugin
- Atlassian Hipchat Integration Plugin Core
Please note, you will need to disable the plugins in the following order else the plugin will be show as disable in the manage-add-ons however it is not save as disable in the database. Also note that removing the Add-Ons will cause Confluence to fall back to the default versions from installations.
Alternatively, upgrade all the Add-Ons to the latest version and leave active as this issue has also been resolved within the Add-ons.
![[Ecosystem JIRA] Bug - A problem which impairs or prevents the functions of the product.](https://ecosystem.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/15303?size=medium "[Ecosystem JIRA] Bug - A problem which impairs or prevents the functions of the product."){kind=small}
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[CONFSERVER-40717] Confluence slow startup because it is trying to start Hipchat plugin which have dependency on another plugin which has been disabled
Hans-Peter Geier
added a comment - Can you fix it also for 5.10? Migration to 6 is not an option to us, due to the unwillingness of Atlassian to listen to their customers. (Discontinuance of the Documentation Theme and the office format viewer plugins, inspite of many complains in this JIRA database which objected to your announcements, and also because you don't fix the known issue with the previewer.)
Hans-Peter Geier
added a comment - Can you fix it also for 5.10? Migration to 6 is not an option to us, due to the unwillingness of Atlassian to listen to their customers. (Discontinuance of the Documentation Theme and the office format viewer plugins, inspite of many complains in this JIRA database which objected to your announcements, and also because you don't fix the known issue with the previewer.) A fix for this issue is now available for Confluence Server customers.
Upgrade now or check out the Release Notes to see what other issues are resolved.
hans-peter.geier It is set as "Awaiting Release". We will update the fix version when releasing Confluence.
Hans-Peter Geier
added a comment - seeing the status has been changed to "Fixed". Which version? Will it be simply a plugin update, so it will resolve the issue on all affected version? (5.10+ ?)
Hans-Peter Geier
added a comment - seeing the status has been changed to "Fixed". Which version? Will it be simply a plugin update, so it will resolve the issue on all affected version? (5.10+ ?) This is a big nuisance. My instance of Confluence server (v6.0.4) takes about 5 minutes to start due to this delay. On the previous version, 5.8.4, it took only about 30 seconds.
Hans-Peter Geier
added a comment - Since it is currently not possible to disable the HipChat plugin without these side effects, I ended up to keep these plugins enabled.
As long as there is no connection to a HipChat server configured in the system admin menu, it has no negative impact to have it enabled while not using it. There is no clue about HipChat to end users even if the plugins are enabled, as long as no HipChat server is set up.
Hans-Peter Geier
added a comment - Since it is currently not possible to disable the HipChat plugin without these side effects, I ended up to keep these plugins enabled.
As long as there is no connection to a HipChat server configured in the system admin menu, it has no negative impact to have it enabled while not using it. There is no clue about HipChat to end users even if the plugins are enabled, as long as no HipChat server is set up. Hans-Peter Geier
added a comment - same in 5.10.8
Hi hans-peter.geier,
It is not possible to backport this fix to 5.10 as it required a significant rework and would likely break compatibility with HipChat.
I have communicated a number of times regarding the office connector on that ticket (unrelated to this ticket), that whilst we have announced it is discontinued there will be plenty of notice given regarding the forthcoming version which it may be removed in. Thus it does not matter if you are on the latest version or otherwise. I have also clearly outlined that we are fully aware of the concerns which you and others have regarding the deprecation, and that is the exact reason we have not removed it sooner.
Similarly, this ticket also has nothing to do with the removal of the Documentation theme. Certainly the removal of the Documentation theme will require some rework for upgrading, something which we have been managing with customers for a considerable period of time before it was removed.
I am happy for you to email me directly to explain your concerns regarding Documentation theme and file previewer, as this single bug is not the right forum for such discussion.
Cheers,
Adam - Confluence Product Manager