Probably the lightest-weight solution for real-time log watching is to use Dancer’s shell in concurrent mode with tail -f: dsh -Mac — tail -f /var/log/apache/*.log The -a is for all machine names that you’ve defined in ~/.dsh/machines.list The -c is for concurrent running of tail The -M prepends the hostname to every line of output.
Have a look at the JavaDoc. The documentation of the PropertyConfiguratorClass (log4j.properties) points out that The PropertyConfigurator does not handle the advanced configuration features supported by the DOMConfigurator such as support custom ErrorHandlers, nested appenders such as the AsyncAppender, etc. So the DOMConfigurator (log4j.xml) offers advanced options. Beside that you can have (at least a … Read more
Works for me with eclipse: <Configuration strict=”true” xmlns=”http://logging.apache.org/log4j/2.0/config” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” xsi:schemaLocation=”http://logging.apache.org/log4j/2.0/config https://raw.githubusercontent.com/apache/logging-log4j2/master/log4j-core/src/main/resources/Log4j-config.xsd”> or against tagged version: <Configuration strict=”true” xmlns=”http://logging.apache.org/log4j/2.0/config” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” xsi:schemaLocation=”http://logging.apache.org/log4j/2.0/config https://raw.githubusercontent.com/apache/logging-log4j2/log4j-2.8.2/log4j-core/src/main/resources/Log4j-config.xsd”>
Remove below jar’s from class path and it should fix the issue – log4j-to-slf4j-2.0.2.jar log4j-to-slf4j-2.0.2-sources.jar log4j-slf4j-impl-2.0.2.jar log4j-slf4j-impl-2.0.2-sources.jar I was able to replicate and fix the issue after downloading apache-log4j-2.0.2 from http://www.apache.org/dyn/closer.cgi/logging/log4j/2.0.2/apache-log4j-2.0.2-bin.zip.
slf4j’s api provides “parameterized logging”, which allows you to do exactly that, although with a slightly different syntax. The example there is: logger.debug(“Value {} was inserted between {} and {}.”, newVal, below, above); For an implementation, you can use Logback which implements slf4j natively, or the slf4j bindings to connect with log4j or other loggers. … Read more
In application.properties you can add ‘logging.level.*=LEVEL’ where ‘LEVEL’ is one of TRACE, DEBUG, INFO, WARN, ERROR, FATAL, OFF. * is responsible for package/class. For example logging.level.root=WARN logging.level.org.springframework.web=DEBUG logging.level.org.hibernate=ERROR This means that root logger has WARN level. org.springframework.web is on DEBUG level, but all hibernates files are logged only ERROR. In your case you must set … Read more
I had a similar problem and just found a way to solve it (by single-stepping through log4j-extras source, no less…) The good news is that, unlike what’s written everywhere, it turns out that you actually CAN configure TimeBasedRollingPolicy using log4j.properties (XML config not needed! At least in versions of log4j >1.2.16 see this bug report) … Read more
Yes, seems there is no such feature. As I understand, it is partly because that logback configuration is more complex so quite difficult to achieve reasonable configuration flexibility by flat string properties. Partly because, imho, it encourages bad practice – placing too many system properties – leads to bloated run-scripts or command lines, more difficult … Read more
Try setting the additivity of the loggers to false. This will avoid the propagation to the rootLogger. log4j.additivity.org.apache=false log4j.additivity.xdasLogger=false
It finds the log4j.xml using the CLASSPATH. If log4j doesn’t find any config file, it will send an error to the console. If you don’t see any such error then it is likely that it is finding a config file which may not be the one you are editing. There is a command-line option to … Read more