ERROR StatusLogger Log4j2 could not find a logging implementation in Jira startup
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
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
During Jira startup the following message is logged in catalina.out:
___ Starting the JIRA Plugin System _________________
[...]
ERROR StatusLogger Log4j2 could not find a logging implementation. Please add log4j-core to the classpath. Using SimpleLogger to log to the console...This doesn't seem to have any negative impact in Jira, however we have the error message logged. If this is present during the plugin start phase, as seen above, it's likely one of the third-party plugins in the instance trying to make use of Log4j2. So far we've identified the following plugins presenting this behavior:
We recommend reaching out to vendor support (link added to plugin name above) for further troubleshooting.