October 2008 - logback-user

TimeBasedRollingPolicy
by Lang, Johannes 18 Mar '09

18 Mar '09

Hello, i'm trying to get a RollingFileAppender with a TimeBasedRollingPolicy working, but i don't succeed. Here's my Appender-Configuration (which i copied from the logback-manual; only changed the layout): <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <File>logFile.log</File> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern>logFile.%d{yyyy-MM-dd_HH-mm}.log</FileNamePattern> </rollingPolicy> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n</Pattern> </layout> </appender> And this is some of the debug-output from the Joran-Configurator: 09:06:48,703 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [FILE] 09:06:48,734 |-INFO in ch.qos.logback.core.joran.action.NestedComponentIA - Pushing component [rollingPolicy] on top of the object stack. 09:06:48,734 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Adding parent to RollingPolicy: FILE 09:06:48,734 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - No compression will be used 09:06:48,734 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Will use the pattern logFile.%d{yyyy-MM-dd_HH-mm}.log for the active file 09:06:48,750 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - The date pattern is 'yyyy-MM-dd_HH-mm' from file name pattern 'logFile.%d{yyyy-MM-dd_HH-mm}.log'. 09:06:48,750 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Roll-over every minute. 09:06:48,750 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[FILE] - Active log file name: logFile.log 09:06:48,750 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Popping appender named [FILE] from the object stack 09:06:48,750 |-INFO in ch.qos.logback.classic.joran.action.LevelAction - root level set to TRACE 09:06:48,750 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [stout] to Logger[root] 09:06:48,750 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [FILE] to Logger[root] 09:06:48,750 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration. Everything seems correct. "Roll-over every minute" is just what i want to do. But what really happens is, that all logging is written to the file "logFile.log". There is no rollover. Any suggestions what's wrong with my appender-config? Cheers Johannes

3 3

Feedback from using Logback in an audit component
by Anders Hammar 04 Nov '08

04 Nov '08

I was asked by Ceki to share my successful Logback story with you all. In a former assignment for one of our customers, we implemented an audit component. The customer is to use this component in their applications to audit end-user activities. In some earlier application specific audit implementations, log4j had been used. However, log4j (and pretty much all existing application logging frameworks that I looked at) has the notion of logging levels. For auditing (at least in this customer's case) we have actions/events which have no relation between them. So, having levels of debug, info, warn, etc isn't right but we rather have independent events. When I found Logback it was kind of love at first sight, the modular design fitted beautifully with what we wanted and we chose Logback (specifically logback-core) for our actual audit logging. We based this choice on two factors in specific: 1. The possibility of log on actions/events rather than levels (as above described) 2. The possiblity of having several independently configured logback instances. (This is not possible with log4j for instance, and as the customer's app server of choice uses log4j we would need to combine application logging and audit logging configuration - which is not good out of security perspective.) Also, the extensive documentation made my work easy to recommend the framework. As we all know, good documentation is not always the case in OSS. However, as mentioned on the mailing list earlier, the lack of a 1.0 release could have been a problem. However, Ceki's track record (with log4j) made me feel safe still going with Logback. As i personally strongly believe in OSS I normally participate and contribute to the community of the libs I use. However, working as a consultant I just can't be involved in everything and tend to only stay active as long as the assignment lasts (there are a few exceptions). Therefore I don't subscribe to this mailing list any longer, but I will monitor this thread so if you have any questions regarding my use case I'll be happy to answer them. /Anders

6 15

Problem with Context Selector: No appenders present in context?
by Joop Vriend 01 Nov '08

01 Nov '08

Hi, I'm having problems using (or configuring?) the logback Context Selector. I followed all the instructions of the manual: http://logback.qos.ch/manual/contextSelector.html But I get the error-message: 20:10:26,365 |-ERROR in Logger[com.ddnh.product.ncmdb] - No appenders present in context [ContextApp-NCMDB] for logger [com.ddnh.product.ncmdb]. And when undeploying also: About to detach context named ContextApp-NCMDB No context named ContextApp-NCMDB was found. I'm using Tomcat 6.0 (with -Dlogback.ContextSelector=JNDI). I placed all the slf4j and logback jars in the TOMCAT_HOME/lib directory: slf4j-api-1.5.5.jar logback-core-0.9.11.jar logback-classic-0.9.11.jar logback-access-0.9.11.jar jul-to-slf4j-1.5.5.jar jcl-over-slf4j-1.5.5.jar janino.jar I edited my web.xml of my webapp "NCMDB": <env-entry> <description>JNDI logging context for this app</description> <env-entry-name>logback/context-name</env-entry-name> <env-entry-type>java.lang.String</env-entry-type> <env-entry-value>ContextApp-NCMDB</env-entry-value> </env-entry> <env-entry> <description>URL for configuring logback context</description> <env-entry-name>logback/configuration-resource</env-entry-name> <env-entry-type>java.lang.String</env-entry-type> <env-entry-value>logback.xml</env-entry-value> </env-entry> <listener> <listener-class>ch.qos.logback.classic.selector.servlet.ContextDetachingSCL</listener-class> </listener> <filter> <filter-name>LoggerContextFilter</filter-name> <filter-class>ch.qos.logback.classic.selector.servlet.LoggerContextFilter</filter-class> </filter> <filter-mapping> <filter-name>LoggerContextFilter</filter-name> <url-pattern>/*</url-pattern> </filter-mapping> And the logback.xml (in WEB-INF/classes) is as follows: <configuration> <evaluator name="WARN_EVALUATOR"> <expression>level == WARN</expression> </evaluator> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <layout class="ch.qos.logback.classic.PatternLayout"> <pattern>%date{yyyy-MM-dd HH:mm:ss} %class %method $%file:%line$%n %level: %message%n%caller{5,WARN_EVALUATOR}%exception{15}</pattern> </layout> </appender> <appender name="RootFileAppender" class="ch.qos.logback.core.rolling.RollingFileAppender"> <append>true</append> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>${catalina.base}/logs/ncmdb.ddnh.%d{yyyy-MM-dd}.log.gz</fileNamePattern> </rollingPolicy> <layout class="ch.qos.logback.classic.PatternLayout"> <pattern>%date{yyyy-MM-dd HH:mm:ss} %class %method $%file:%line$%n %level: %message%n%caller{5,WARN_EVALUATOR}%exception{15}</pattern> </layout> <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>DEBUG</level> </filter> </appender> <logger name="com.ddnh.product.ncmdb" additivity="false"> <level value="DEBUG"/> <appender-ref ref="RootFileAppender"/> <appender-ref ref="RootEmailAppender"/> </logger> <root> <level value="DEBUG"/> <appender-ref ref="STDOUT" /> <appender-ref ref="RootFileAppender"/> <appender-ref ref="RootEmailAppender"/> </root> </configuration> What am I doing wrong?? Any help is appreciated. Thanks, Joop.

2 1

Socket
by Greg Flex 31 Oct '08

31 Oct '08

Hi Guys, I'd like to find out what is the maximum file size I can send over the network with the client-server appenders idea. I'm using it at the moment and when sending more than, it seems like 252 bytes, on the server side I'm getting an exception: Caught java.net.SocketException closing connection. The file with 252 OR smaller will get written (or printed to the console) however at the end I still get the exception (when the connection if closed). I'm trying to run the client on one computer and server on another (it's not localhost etc.). With the socket I can write the a file and store them on the server's HD with the speed as if they were processed/written locally. So the performance is great... I'm just not getting any data bigger the above stated 252 bytes. The file I'm trying to transfer over and log is about 3.4KB. Can someone help Thanks Greg.

2 3

Re: [logback-user] Set Level per Logger AND Appender?
by Robert Elliot 31 Oct '08

31 Oct '08

It sounds like that would allow the behaviour I would need, thanks very much, I'll use that in future. I have to confess, however, that it feels rather messy and complicated to maintain. What do you think of the idea of specifying a level on the combination of logger and appender (effectively the appender-ref)? With the proviso that you can still specify it on the logger alone as a shorthand for specifying it on all appender-refs? I'm tempted to protoptype it if you would consider the approach; it would allow a nice clean configuration based on inheritance, and would work with existing logback.xml files as well. ----- Original Message ----- From: "Ceki Gulcu" <listid(a)qos.ch> To: "logback users list" <logback-user(a)qos.ch> Sent: Thursday, 30 October, 2008 1:51:42 PM GMT +00:00 GMT Britain, Ireland, Portugal Subject: Re: [logback-user] Set Level per Logger AND Appender? I see. You could attach an evaluator fiter which can filter events based on criteria that you decide upon. For example, <filter class="ch.qos.logback.core.filter.EvaluatorFilter"> <evaluator name="myEval"> <expression> (logger.getName().contains("logger names...") && level > INFO) || (level > WARN) </expression> </evaluator> <OnMismatch>DENY</OnMismatch> <OnMatch>ACCEPT</OnMatch> </filter> where "logger names ..." stands for loggers needing special handling. I am not 100% the above expression is error free but it should at least get my point across. In particular, you need to write & as & in an XML file. So '&&' would become '&&'. Does the above help? Robert Elliot wrote: > Because for some loggers I want INFO level statements to be written > to application.log (for instance in the case of server startup / > shutdown) and for some loggers I don't. If I set a filter on the > appender to only allow WARN or higher to application.log I lose all > the INFO statements I wanted- if I set it to allow INFO or higher then > if I set a logger to DEBUG then it will start sending INFO messages > that I don't want to application.log. -- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch _______________________________________________ Logback-user mailing list Logback-user(a)qos.ch http://qos.ch/mailman/listinfo/logback-user

2 3

Logging to Oracle with DBAppender and connection pooling doesn't work
by Morten Egelund Rasmussen 31 Oct '08

31 Oct '08

Hi all, Does anybody have a working example on how to log to Oracle with a connection pool on a Tomcat server? I have the following: In Tomcat's server.xml: <Resource name="jdbc/logger" auth="Container" type="javax.sql.DataSource" driverClassName="oracle.jdbc.OracleDriver" url="foo" username="foo" password="foobar" maxActive="50" maxIdle="5" initialSize="10" maxWait="-1" removeAbandoned="true" validationQuery="select 1 from dual"/> In Tomcat's context.xml: <ResourceLink name="jdbc/logger" global="jdbc/logger" type="javax.sql.DataSource"/> I have defined the following Logback appenders: <appender name="db" class="myAppenderClass"> <connectionSource class="ch.qos.logback.core.db.JNDIConnectionSource"> <param name="jndiLocation" value="java:comp/env/jdbc/logger" /> </connectionSource> </appender> <appender name="db2" class="myAppenderClass"> <connectionSource class="ch.qos.logback.core.db.DriverManagerConnectionSource"> <driverClass>oracle.jdbc.driver.OracleDriver</driverClass> <url>foo</url> <user>foo</user> <password>foobar</password> </connectionSource> </appender> .....where "myAppenderClass" is an appender class as described here: http://jira.qos.ch/browse/LBCORE-15 Using the "db" appender gives nothing, but using the "db2" appender gives lots of output. What am I missing? Any ideas? ~Morten :-/

3 4

Adding a timestamp to a FileAppender file
by nicolas.giraud＠bnf.fr 30 Oct '08

30 Oct '08

Hi, I have just switched from log4j to logback. I would like to generate log containing results output by my program, and I want the file name to be SomePrefix.<timestamp>.someExt. I can do this programmatically but I'd like, if possible, to have all my logging configuration in my logback.xml file. Here's the appender I declared : <appender name="resultFile" class="ch.qos.logback.core.FileAppender"> <file>${logFolder}/SomePrefix.%d.someExt</file> <append>false</append> <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>info</level> </filter> <layout class="ch.qos.logback.classic.PatternLayout"> <pattern>%m%n</pattern> </layout> </appender> However the %d pattern is not interpreted, is there a way to do this? Maybe using a RollingFileAppender, but I don't see how. Regards, Nicolas Avant d'imprimer, pensez � l'environnement. Consider the environment before printing this mail.

4 5

Set Level per Logger AND Appender?
by Robert Elliot 30 Oct '08

30 Oct '08

Hi, A common use case for me with log4j and now LogBack is that I want to have a default logging setup appending to a (set of) file(s) - typically this will be a root logger with level warn appending to say application.log. I will then tweak sub loggers to get exactly the output I want - info in some places, error in others, so I get sufficient feedback to see e.g. server startup and shutdown but otherwise I only see things that are genuinely a potential problem. I consider this config part of the normal working operation of the application, and expect to be able to retrieve the expected output at any point in the future. It's a system problem if any of that output is lost or if the application.log is polluted with other log statements. I then frequently want to set up more detailed debug logging for a subset of the system - indeed I'm writing an Ajax based web console to allow logging to be configured and output seen on the fly, having written an aspectJ based trace logging aspect. The problem I experience is that if I set a Logger, using the normal class based naming scheme, to level "DEBUG" then it will log at that level to application.log as well as my debug appender, littering the application.log file with message I do not want recorded there. If I turn additivity to false for that logger then it will no longer send WARN messages to the application.log appender, losing the record of all system problems that I expect application.log to contain. Does that make sense? I hope it seems a reasonable use case. If so, what would be considered the best practice for achieving this? In log4j I would overcome this by creating a new appender that also appends to application.log, assigning it to the logger I wanted to use for debug and giving it an appropriate threshold to maintain the general contract of application.log, and then setting the logger's additivity to false. This, however, is a very crude solution involving a great deal of additional configuration and is very fragile - any alterations to what I consider the "normal" logging behaviour of my system may well require me to alter all debug configuration. (What I really want is to specify levels on the combination of a logger and an appender rather than just on a logger. This would allow taking advantage of the inheritance system - the combination of root logger and application.log appender's level of WARN would then be inherited (and could be over-ridden, of course) by all loggers, and adding a new debug appender to a logger and setting the level of that logger & appender combo to DEBUG would not affect what was sent to application.log at all. If I were to work on making that possible in Logback, would that alteration be considered, or is that seen as undesirable?) Regards, Robert

2 3

Consol plugin via update site
by Szel, Zoltan (IT) 30 Oct '08

30 Oct '08

Hi all, i would like to make the Consol plugin available for our developers and i am wondering if there is an update site what i can recommend for them. I made a bit of googling and haven't found anything. Is there a plan to make the plugin available via an update site? Thanks in advance! Best Regards, Zoltan Szel -------------------------------------------------------- NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error.

2 1

multiple webapps and jmxConfigurator
by Jean-Luc Geering 30 Oct '08

30 Oct '08

Hi All, I have multiple webapps deployed in the same tomcat instance, each with it's own logback.xml, and I'm wondering what will happen if I enable the <jmxConfigurator/> for all of them. Will they all share the same Configurator MBean ? Will I be able to configure the log levels for only one of them ? Thanks a lot, JL

4 4