December 2006 - logback-user

Using logback in tomcat
by Michael Abato 17 Apr '07

17 Apr '07

I'm successfully using logback with Tomcat and have a small suggestion that will help people with complex deployments: look for logback-access.xml in system property catalina.base rather than catalina.home. Tomcat is intentionally setup such that multiple instances (java VMs) can be running off the same copy of the tomcat distribution and set up private CATALINA_BASE directories for server config, logs, temp space, etc. Such setups will naturally want to configure logback in CATALINA_BASE, not in the (potentially read-only) CATALINA_HOME. In cases where the user does *not* set CATALINA_BASE, it takes the same value as CATALINA_HOME (which is generally the same as TOMCAT_HOME). I've patched the source of LogbackValve.java to do this and it works well. The change of "catalina.home" to "catalina.base" is to trivial for a formal patch... On a related note, I've also configured tomcat to use log4j/logback for internal logging, which also works quite well. I noticed in a previous post you "don't recommend this at this time" and would like to know the reason(s). Routing *all* logging through one logger/one config, which in turn can separate "live" logs from rotated out "archive" logs in a separate directory is a godsend. I'm assuming it is because doing this requires mucking around with the tomcat startup scripts to replace ACL from the very beginning of the tomcat boot process. I'd already created a "boot" directory with a dynamic set of jar's and classes (for unrelated reasons) so switching ACL to log4j/logback was pretty trivial for me. Is there more to the reluctance than the fact that there is no "drop in" way to do it? If there's interest, I can tidy up my tomcat patch and post the details. -- View this message in context: http://www.nabble.com/Using-logback-in-tomcat-tf2890321.html#a8074672 Sent from the Logback User mailing list archive at Nabble.com.

2 2

[ANN] Release of logback 0.7.1
by Sebastien Pennec 23 Jan '07

23 Jan '07

December 19th, 2006 - Release of version 0.7 Version 0.7.1 of logback has been released. This version contains more detailled information about logback access module, and its JMX components. A dedicated page[1] explains how to configure and use logback access in Tomcat and Jetty, and access some of its components via JMX. Links: [1] http://logback.qos.ch/access.html -- Sébastien Pennec sebastien(a)qos.ch Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch/

1 1

How To Use Filters
by Yoram Forscher 04 Jan '07

04 Jan '07

After reading chapter 6, "Filter Chains," I tried to use some filters myself with no success. My configuration file contains the following: <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <filter class="ch.qos.logback.core.filter.EvaluatorFilter"> <evaluator name="myEval"> <expression>marker.getName().equals("printConfiguration")</expression> </evaluator> <OnMismatch>NEUTRAL</OnMismatch> <OnMatch>DENY</OnMatch> </filter> <layout class="ch.qos.logback.classic.PatternLayout"> <param name="pattern" value="%d{ISO8601} %-5p [%c{40}] %m%n"/> </layout> </appender> In my code I have the following: private Marker pcMarker = MarkerFactory.getMarker("printConfiguration"); ... logger.debug(pcMarker, "Configuration Information"); ... I expect in that case that no output will be created, but it keeps printing it regardless of how I set it up. I also tried to change the expression to 'marker.contains("printConfiguration")' and change the OnMismatch and OnMatch both to DENY. Same result. What am I doing wrong?

4 15

Why LGPL instead of Apache License?
by bsnyder 27 Dec '06

27 Dec '06

Log4J employs the Apache License and wound up being the inspiration for the entire Logging Project at the ASF, why was the LGPL chosen as the license to employ for Logback? -- View this message in context: http://www.nabble.com/Why-LGPL-instead-of-Apache-License--tf2884320.html#a8… Sent from the Logback User mailing list archive at Nabble.com.

2 1

Trouble setting up logback in tomcat.
by Marten Deinum 21 Dec '06

21 Dec '06

For my current project I would like to switch out all the logging which is currently being done by log4j and here en there by commons-logging to one framework. After some searching I discoverd SLF4J and Logback as the successor to log4j. In your code I swapped out all the log4j and commons-logging to the SLF4J api and I want to use Logback as my logger. I converted our log4j.properties file with the configuration converter on the website, so I assume that is correct. In the tomcat directory I have the following logging libs (I want tomcat to use SLF4J to) commons/lib/commons-logging-1.1.jar commons/lib/jcl104-over-slf4j-1.1.0-RC1.jar commons/classes/logback.xml In our webapplication (which is a packaged war and doesn't get unpacked!) I have WEB-INF/lib/slf4j-api-1.1.0-RC1.jar WEB-INF/lib/logback-classic-0.7.jar WEB-INF/lib/logback-core-0.7.jar WEB-INF/classes/logback.xml The contents of the logback.xml in the commons directory just contains a simple ConsoleAppender and is configured to WARN level. The file in the WEB-INF directory is configured as a file which should be written to c:\logs\mylog.log, configured different levels for different packages we use. However logback isn't getting picked up, everything is being logged by the java.util classes (as it appears thatone is being initialized by tomcat instead of the logback logger). I tried different configurations, all the logback/slf4j jars in the commons/lib and one config file in commons/classes. Different jars in commons/lib and WEB-INF/lib but until now everytime with the same result, only logging to JUL and nothing to logback and my configured logfile. Currently I'm at a loss on what to do and how to make it work. I need some assistance with this. Kind Regards, Marten -- View this message in context: http://www.nabble.com/Trouble-setting-up-logback-in-tomcat.-tf2858698.html#… Sent from the Logback User mailing list archive at Nabble.com.

3 8

[ANN] Release of logback 0.7
by Sebastien Pennec 18 Dec '06

18 Dec '06

December 18th, 2006 - Release of version 0.7 Version 0.7 of logback has been released. Logback now ships with a new module: log4j-bridge. This new module can be used to intercept log4j calls and redirects them to logback components. More information about this module can be found in the corresponding documentation page[1]. The documentation has been vastly updated. Two new chapters, namely Filters and MDC, are available in the manual section[2]. Links: [1] http://logback.qos.ch/bridge.html [2] http://logback.qos.ch/manual/index.html -- Sébastien Pennec sebastien(a)qos.ch Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch/

1 0

We are on IRC
by Ceki Gülcü 15 Dec '06

15 Dec '06

Hello all, In case you wish to reach us by IRC, Sebastien and I are often available at irc.freenode.net#logback Cheers, -- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch

1 0

loggingPermission
by charles gay 04 Dec '06

04 Dec '06

Hi, one major advantage(to me, i acknowledge ;-) ) of the java.util.logging package over log4j and other logging libraries is its security. it uses the underlying java security infrastructure by securing logs with loggingpermission use. have you any plan to use loggingpermission? it can be used very easily to control any logging configuration change. other use case can stands on loggingpermission to prevent some programers to use loggers of some packages for example. if you are interested to implemented this feature, i can help you to understand java security internals if needed. cheers, Charles GAY www.jguard.net -- View this message in context: http://www.nabble.com/loggingPermission-tf2731649.html#a7619191 Sent from the Logback User mailing list archive at Nabble.com.

2 2