Unable to enable Team Calendars for Confluence with the error "Configuration problem: Unable to locate Spring NamespaceHandler for XML schema"

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

Problem

The plugin, Team Calendars for Confluence, is unable to be enabled from the Add-On Manager in Confluence Admin. This typically occurs after a plugin update.

The following appears in the atlassian-confluence.log:

1 2 3 4 5 6 ERROR [ThreadPoolAsyncTaskExecutor::Thread 39] [extender.internal.activator.ContextLoaderListener] onOsgiApplicationEvent Application context refresh failed (NonValidatingOsgiBundleXmlApplicationContext(bundle=com.atlassian.confluence.extra.team-calendars, config=osgibundle:/META-INF/spring/*.xml)) – referer: http://localhost:8090/confluence/plugins/servlet/upm | url: /rest/plugins/1.0/com.atlassian.confluence.extra.team-calendars-key | userName: admin org.springframework.beans.factory.parsing.BeanDefinitionParsingException:   Configuration problem: Unable to locate Spring NamespaceHandler for XML schema namespace http://www.springframework.org/schema/context Offending resource: URL [bundle://219.0:0/META-INF/spring/spring-components.xml]

Cause

The plugin is trying to load a resource that has somehow been corrupted in the cache.

Resolution

Try to Clear the plugin cache, so that the plugins are forced to load these resources directly from the .jar files

Updated on April 11, 2025

Still need help?

The Atlassian Community is here for you.