After updating an App some functions may not be available or render incorrectly
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
After updating App in Confluence, you may find that certain functions related to that App do not render correctly.
Diagnosis
Additionally, the following appears in the atlassian-confluence.log
1
2
ERROR [ajp-bio-8009-exec-142] [plugin.descriptor.web.ConfluenceWebInterfaceManager] getHtml Failed to render web panel: com.atlassian.plugin.web.descriptors.DefaultWebPanelModuleDescriptor$ContextAwareWebPanel@a99a6ea
org.springframework.osgi.service.importer.ServiceProxyDestroyedException: service proxy has been destroyedExamine the full stack trace to find class names similar to the App that have been recently updated.
1
2
3
4
5
6
7
...
at com.sun.proxy.$Proxy2565.getBaseUrl(Unknown Source)
at com.atlassian.upm.license.storage.lib.ThirdPartyPluginLicenseStorageManagerImpl.getPluginManagementUri(ThirdPartyPluginLicenseStorageManagerImpl.java:219)
at com.vendor.plugin.confluence.license.vendorLicenseManager.getLicenseManagementURL(GliffyLicenseManager.java:153)
at com.vendor.plugin.confluence.panel.FooterContextProvider.getContextMap(FooterContextProvider.java:44)
at com.atlassian.plugin.web.descriptors.DefaultWebPanelModuleDescriptor$ContextAwareWebPanel.getHtml(DefaultWebPanelModuleDescriptor.java:144)
...Note: plugin.descriptor.web.ConfluenceWebInterfaceManager was called just before the faulty App - this is a good way to ensure you're looking at the correct App, to verify that you have correctly identified the App, Disabling or Enabling a Plugin. The logs should show no more entries. You may see similar entries, depending on how many Apps are affected by this problem. Repeat the diagnosis until all affected Apps have been identified.
Cause
App or app module failed to install / update properly
Solution
Ensure that the Universal Plugin Manager Unable to update the Universal Plugin Manager (UPM)
Uninstall the offending Add-ons via the Universal Plugin Manager
Reinstall the correct version of the offending App
Was this helpful?