Team Calendars for Confluence No Longer Renders After Updating the Plugin

Related content

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.

Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles 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

Symptoms

The Team Calendars for Confluence page is now displayed as $calendarhtml:


Variations of the following appear in the atlassian-confluence.log:

2015-01-14 12:32:06,835 ERROR [http-bio-8090-exec-196] [common.error.jersey.ThrowableExceptionMapper] toResponse Uncaught exception thrown by REST service: bundle [com.atlassian.confluence.extra.team-calendars]
 -- url: /rest/calendar-services/1.0/calendar/export/subcalendar/private/c902c90afb7b1e44df02fc0a6f796cb97a7b81fd.ics | userName: anonymous
com.atlassian.activeobjects.internal.ActiveObjectsInitException: bundle [com.atlassian.confluence.extra.team-calendars]
	at com.atlassian.activeobjects.osgi.TenantAwareActiveObjects$1$1$1.call(TenantAwareActiveObjects.java:105)
	at com.atlassian.activeobjects.osgi.TenantAwareActiveObjects$1$1$1.call(TenantAwareActiveObjects.java:92)
	at com.atlassian.sal.core.executor.ThreadLocalDelegateCallable.call(ThreadLocalDelegateCallable.java:42)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.IllegalStateException: Cannot create object because the plugin container is unavailable for bundle 'com.atlassian.confluence.extra.team-calendars'

2016-03-02 16:57:17,425 ERROR [http-bio-8090-exec-2357] [common.error.jersey.ThrowableExceptionMapper] toResponse Uncaught exception thrown by REST service: Cannot uninstall 'com.atlassian.confluence.extra.team-calendars'
 -- url: /rest/plugins/1.0/com.atlassian.confluence.extra.team-calendars-key | userName: USER | referer: https://HOST:PORT/plugins/servlet/upm
com.atlassian.plugin.osgi.container.OsgiContainerException: Cannot uninstall 'com.atlassian.confluence.extra.team-calendars'
	at com.atlassian.plugin.osgi.factory.OsgiPlugin.uninstallInternal(OsgiPlugin.java:609)

Cause

The updated Team Calendars for Confluence is corrupt.

Workaround

Clear the Confluence plugins cache

Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.

Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles 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

If the Confluence apps cache gets out of sync or corrupted, it can cause your apps to stop working correctly. This can affect the performance and stability of Confluence Data Center.

Steps to clear the apps cache

Repeat these steps on each node, one by one.

  1. Shutdown Confluence.
  2. Ensure the user running Confluence has full read/write privileges to the confluence-home directory.

  3. Delete the following directories in the Confluence home directory:

    This will remove the app cache files only and will not permanently remove any apps. These directories will be recreated during the next Confluence startup.  However, some third-party apps may store metadata in these directories, so we recommend creating a temporary backup of the directories.
    • <confluence-home>/bundled-plugins
    • <confluence-home>/plugins-cache
    • <confluence-home>/plugins-osgi-cache
    • <confluence-home>/plugins-temp
    • <confluence-home>/bundled-plugins_language (in recent Confluence versions, you may not see this directory. It's safe to skip.)
  4. Start Confluence

When all nodes are done, you can optionally reset all Confluence apps back to their default state through the database if any of the apps are still generating lots of log errors or are not working correctly.

Related topics
DescriptionTo clear the Confluence plugins cache when it gets out of sync or corrupted.
ProductConfluence
Platform

Cloud

Resolution

Last modified on Dec 18, 2024

Was this helpful?

Yes
No
Provide feedback about this article

Related content

Powered by Confluence and Scroll Viewport.