-
Bug
-
Resolution: Fixed
-
Medium
-
10.1.2, 10.3.2
-
10.01
-
3
-
Severity 3 - Minor
-
47
-
Issue Summary
When starting up a Jira Service Management environment without any modifications, the following message can be seen in the startup logs:
... SLF4J(E): A service provider failed to instantiate: org.slf4j.spi.SLF4JServiceProvider: Provider org.apache.logging.slf4j.SLF4JServiceProvider not found ...
Quoting the SLF4J warning or error messages and their meanings reference about this topic:
This message is a warning and not an error. It is reported when no SLF4J providers could be found on the class path. SLF4J requires a logging provider because it is a logging API and not an logging implementation. Placing one (and only one) of the many available providers such as slf4j-nop.jar slf4j-simple.jar, slf4j-reload4j.jar, slf4j-jdk14.jar or logback-classic.jar on the class path will solve the problem.
In the absence of a provider, SLF4J will default to a no-operation (NOP) logger provider.
While no impact can be observed, we should suppress this warning.
Steps to Reproduce
- Start a Jira Service Management instance
- Check $JIRA_INSTALL/logs/catalina.out
Expected Results
No warnings are thrown.
Actual Results
A org.apache.logging.slf4j.SLF4JServiceProvider not found warning will appear on catalina.out
Workaround
No workaround available
- links to
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|