System Plugin is Failing to Load

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

Problem

There may be multiple symptoms in this case:

  • JIRA may fail to startup with plugin errors

  • JIRA successfully starts up, but some functionality is missing

JIRA logs show something like this:

1 2 3 4 5 6 7 8 9 10 11 12 2016-11-19 07:48:36,420 ThreadPoolAsyncTaskExecutor::Thread 12 ERROR [c.a.p.osgi.factory.OsgiPlugin] Unable to start the plugin container for plugin 'com.atlassian.crowd.embedded.admin' org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter#0': Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter]: Constructor threw exception; nested exception is javax.xml.transform.TransformerFactoryConfigurationError: Provider for class javax.xml.transform.TransformerFactory cannot be created ... Caused by: java.util.ServiceConfigurationError: javax.xml.transform.TransformerFactory: Provider org.apache.xalan.processor.TransformerFactoryImpl not found at java.util.ServiceLoader.fail(ServiceLoader.java:239) at java.util.ServiceLoader.access$300(ServiceLoader.java:185) at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:404) at java.util.ServiceLoader$1.next(ServiceLoader.java:480) at javax.xml.transform.FactoryFinder$1.run(FactoryFinder.java:328) at java.security.AccessController.doPrivileged(Native Method) at javax.xml.transform.FactoryFinder.findServiceProvider(FactoryFinder.java:323) ... 28 more

Diagnosis

Diagnostic Steps

Examining startup configuration details we notice something like this in Java startup parameters:

1 -Datlassian.org.osgi.framework.bootdelegation=META-INF.services,com.yourkit,com.singularity.*,com.jprofiler,com.jprofiler.*,org.apache.xerces,org.apache.xerces.*,org.apache.xalan,org.apachexalan.*,sun.*,com.sun.jndi,com.icl.saxon,com.icl.saxon.*,javax.servlet,javax.servlet.*,com.sun.xml.bind.* -javaagent:/opt/AppDynamics/AppServerAgent-4.1.7.2/javaagent.jar

Cause

OSGI bootstrap has been modified, which controls the plugin startup process. In this case, the modification was misconfigured, resulting in missing class dependencies.

Solution

Resolution

  • Examine the Java parameters to ensure that it is correctly configured

    OR

  • Remove the -Datlassian.org.osgi.framework.bootdelegation parameter

  • Restart JIRA

Updated on April 2, 2025

Still need help?

The Atlassian Community is here for you.