- logback-user - mailman3.qos.ch

Setting log filename during runtime
by Jenny 07 Nov '08

07 Nov '08

Hello, How can i set the log filename set during the init() of my StartupServlet. I tried using MDC but it's not working for me. What happens is the file is not created. Instead a file with name "%exp{logFileName}" is created on my web server's bin directory. In my StartupServlet, I have this init method that calls MDC.put(). public void init() throws ServletException { MDC.put("logFileName", "c:\\testlogs\\test.log"); Logger log = LoggerFactory.getLogger(StartupServlet.class); log.info("This should be logged"); } In my logback.xml, I have a MDC.get(). <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <append>true</append> <expression name="logFileName">MDC.get("logFileName")</expression> <file>%exp{logFileName}</file> ... I'm new with logback, thanks in advance for your help! I'm trying to follow Ceki's example in his blog http://ceki.blogspot.com/2006/10/repated-configuration-with-joran.html thanks, jenny

1 0

NPE in Logback JMX Configurator
by Jean-Luc Geering 07 Nov '08

07 Nov '08

Hi there, Has anybody had a chance to look at http://jira.qos.ch/browse/LBCLASSIC-78and http://jira.qos.ch/browse/LBCLASSIC-79 ? They don't seem to be overly complex issues and it would be great to have them fixed in the next logback release. JL

2 2

Logback configuration
by Natan Cox 06 Nov '08

06 Nov '08

Hi all, Is there a way to specify the file substitution propery as something configurable? So I would not do <configuration> <substitutionProperty file="variables1.properties" /> but <configuration> <substitutionProperty file="*${logback.properties}*" /> where in Java I would have to specify something like java Main -Dlogback.properties=c:/project/Main/main.properties to be able to run my application? Typically I want to have one configuration file, but sometimes I use multiple files to be able to turn on/off certain functionalities. I'm also thinking of moving the logback properties into my application properties file (not sure yet). This configuration option would allow me to achieve this. Thanks, Natan

2 2

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

SocketAppender
by Greg Flex 03 Nov '08

03 Nov '08

Hi all, So I still have some problems with the socketAppender. I'm using the server and the client (sample code) that comes with the Logback. I'm sending a string to a server that is about 4KB in size. (in the "for" loop) When I'm executing this "for" loop once or twice or even 4 times nothing gets transmitted from the client to the server. I get nothing just a message that server is waiting for data, then I get message saying that the socket connections has been closed. Now, when I'm executing the same exactly code and I'm running the same loop (that sends the 4KB string over to the server) but say 10 or more times, everything works! I'm not an expert on how TCP/IP works but it looks to me that the socket closes the connection before the data I'm sending gets actually transmitted to the server. How do I keep the socket open until the data gets to the server? Any suggestion? Thanks Greg

3 7

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