Issue
This Content is from Stack Overflow. Question asked by Jongbum Lee
(prev question : What does the below mean in logback’s logger?)
I’m currently struggling with a log library crash.
Deployed the same .war file on both tomcat servers, everything is the same.
On Server A, the org.springframework.* logs are properly logged.
No org.springframework.* logs are logged on Server B.
In Server B, if log4j-api-2.7.1.jar is not loaded by renaming, org.springframework.* log is recorded.
In what cases can this happen?
If anyone knows, please let me know.
my WEB-INF/lib directory about log, slf4j jar file
common-logging-1.2.jar
jboss-logging-3.4.1.Final.jar
log4j-api-2.17.1.jar
log4j-over-slf4j-1.7.32.jar
logback-classic-1.2.10.jar
logback-core-1.2.10.jar
jcl-over-slf4j-1.7.21.jar
jul-to-slf4j-1.7.32.jar
log4j-over-slf4j-1.7.32.jar
slf4j-api-1.7.21.jar
Solution
The logger names are typically the fully qualified class names of the classes where the logger is created. These names include the package name followed by the class name. They are abbreviated, starting from the left, to make them fit a particular text width. The o.s. abbreviation stands for org.springframework. And in your Group B, o.m. stands for org.mybatis.
This Question was asked in StackOverflow by Jongbum Lee and Answered by k314159 It is licensed under the terms of CC BY-SA 2.5. - CC BY-SA 3.0. - CC BY-SA 4.0.