JIRA Startup fails with java.lang.NoSuchMethodError: org.slf4j.spi.LocationAwareLogger.log

Still need help?

The Atlassian Community is here for you.

Ask the community

Symptoms

This problem is related to a third party plugin, and therefore not supported by Atlassian. See Atlassian Supported Plugins for more information.

In MAC OS based systems, after extracting the .tar.gz bundle of JIRA and attempting to start JIRA results in the below error in the the atlassian-jira.log:

An Error occurred during ComponentContainerLauncher servlet context initialisation - org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;[Ljava/lang/Object;Ljava/lang/Throwable;)V.
java.lang.NoSuchMethodError: org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;[Ljava/lang/Object;Ljava/lang/Throwable;)V
	at org.apache.commons.logging.impl.SLF4JLocationAwareLog.info(SLF4JLocationAwareLog.java:159)
	at org.quartz.core.QuartzScheduler.<init>(QuartzScheduler.java:195)
	at org.quartz.impl.StdSchedulerFactory.instantiate(StdSchedulerFactory.java:972)
	at org.quartz.impl.StdSchedulerFactory.getScheduler(StdSchedulerFactory.java:1152)
	at com.atlassian.jira.scheduler.JiraSchedulerFactory.getScheduler(JiraSchedulerFactory.java:27)
	at com.atlassian.jira.ContainerRegistrar.registerComponents(ContainerRegistrar.java:1542)
	at com.atlassian.jira.ComponentManager.registerComponents(ComponentManager.java:374)
	at com.atlassian.jira.ComponentManager.initialise(ComponentManager.java:185)

Cause

The JRE available in MAC OS allows to add extensions directly to the JVM runtime by copying the appropriate .jar  files to the path /Library/Java/Extensions/. The jar files at this location can result in conflicts with the bundled jar files that comes with the application.

Resolution

To verify and correct the same please follow the below steps:

  • Execute the command ls /Library/Java/Extensions/ and check whether there are any jar files which has slf4j in their file name
  • If yes, move them to another path (do not delete as it may be needed by other applications already installed in the the system)
  • Start JIRA and this error should be resolved.

Last modified on Mar 30, 2016

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.