JIRA Fails to Start due to Could not instantiate appender

Still need help?

The Atlassian Community is here for you.

Ask the community

Symptoms

JIRA fails to startup and the following appears in the atlassian-jira.log:

log4j:ERROR Could not instantiate appender named "soapdumplog".
log4j:ERROR Could not instantiate class [com.atlassian.jira.logging.MultiTenantJiraHomeAppender].
log4j:ERROR Could not instantiate appender named "filelog".
log4j:ERROR Could not instantiate class [com.atlassian.jira.logging.MultiTenantJiraHomeAppender].
log4j:ERROR Could not instantiate appender named "sqllog".
java.lang.ClassNotFoundException: com.atlassian.jira.logging.MultiTenantJiraHomeAppender

log4j:ERROR Could not instantiate appender named "slowquerylog".

Cause

Certain extraction tools have been known to cause issues when uncompressing files with long names. This causes incomplete extractions and will result in JIRA missing essential files to run.

Workaround

  • Windows:  
    • Avoid using Windows' built-in file extraction tool and WinRAR. 
    • A popular and free alternative is 7zip.

  • Unix
    • Avoid using Solaris' default tar utility. 
    • Please use the GNU tar as an alternative when extracting.
Last modified on Apr 7, 2016

Was this helpful?

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