This Short introduction to log4j guide is a little bit old but still valid. That guide will give you some information about how to use loggers and appenders. Just to get you going you have two simple approaches you can take. First one is to just add this line to your main method: Second approach is to … Read more
Samudra Gupta explains in his book1: The Logger object is the main object that an application developer uses to log any message. The Logger objects acting within a particular instance of an application follow a parent-child hierarchy. If you have the following configuration: This is how the logger hierarchy could end up looking:2 Samudra Gupta continues to explain: At the … Read more
Use this if your code or some libraries you are using uses Log4j directly, but you want to use a different SLF4J binding than Log4j. It will route the Log4j API calls to SLF4J to the binding you choose. You need to remove the Log4j library from your classpath and replace it with this dependency. Use … Read more
By default, a logger inherits the appenders from its ancestors. By setting additivity=”false”, you prevent this behaviour. In your example, there may be appenders associated with com.mypage.glass or com.mypage or even the root logger that would be inherited if you don’t set that property to false.
Alright, so I got it working by changing this to this Apparently you have to specify the logging level to the rootLogger first? I apologize if I wasted anyone’s time. Also, I decided to answer my own question because this wasn’t a classpath issue.
Those messages are something tricky, enough so that people created this to make it clearer: https://issues.apache.org/bugzilla/show_bug.cgi?id=25747 What’s tricky about them is that the warnings are written if Log4j can’t find its log4j.properties (or log4j.xml) file, but also if the file is fine and dandy but its content is not complete from a configuration point of view. The following paragraph … Read more