March 2009 - logback-user - mailman3.qos.ch

What's outdated, the doc or the plugin ?
by pierre8r-nabble＠yahoo.fr 18 Mar '09

18 Mar '09

Hello, About the the console plugin, you write on LogBack site : Unfortunately, the console plugin is somewhat outdated. It expects logback version 0.9.9. It will be upgraded in the coming weeks. I try it with : ch.qos.logback.eclipse_1.1.0.zip logback-0.9.15.zip Eclipse 3.4.1 And it seen to work. What's outdated, the doc or the plugin ? Regards, Pierre8r

2 1

From Log4J to LogBack. PropertyConfigurator.configure("log4j.properties");
by pierre8r-nabble＠yahoo.fr 18 Mar '09

18 Mar '09

Hello, How can I write for Logback this Java code for Log4J ? public static void main(String[] args) { PropertyConfigurator.configure("log4j.properties"); Regards, Pierre8r

2 1

Multiple files and other issues (part 2)
by m.bresciani＠email.it 13 Mar '09

13 Mar '09

Hello all, I've tried to follow the guidelines and added the file Ceki suggested me. Anyway, it seems that the special package (here below "com.alcatel.wtd.neto") does not go into itst own file (here below "trace/NEtO.log) but remains in the main one (here below "trace/WebEML:log"). Any idea? This is it: <configuration debug="true">     <appender name="WebEML" class="ch.qos.logback.core.FileAppender" > <file>trace/WebEML.log</file> <append>false</append>   <layout> <pattern>%d{yyyy-MM-dd HH:mm:ss},%p,%c,%F,%C{1} %m%n</pattern> </layout> </appender>  <appender name="NEtO" class="ch.qos.logback.core.FileAppender" > <file>trace/NEtO.log</file> <append>false</append> <layout> <pattern>%d{yyyy-MM-dd HH:mm:ss},%p,%c,%F,%C{1} %m%n</pattern> </layout> </appender>     <logger name="com.alcatel.wtd.neto" additivity="false"> <appender-ref ref="NEtO"/> </logger>  <root level="DEBUG"> <appender-ref ref="WebEML"/> </root> </configuration> Thanks, Marco -------------------------------------------------------------------- mail2web.com What can On Demand Business Solutions do for you? http://link.mail2web.com/Business/SharePoint

3 4

Re: [logback-user] Multiple files and other issues (part 2)
by m.bresciani＠email.it 11 Mar '09

11 Mar '09

Not yet, I've sent the configuration and the log file to the list, yesterday, and I'm still trying to modify it to understand. Marco Original Message: ----------------- From: Ceki Gulcu ceki(a)qos.ch Date: Wed, 11 Mar 2009 11:56:32 +0100 To: logback-user(a)qos.ch Subject: Re: [logback-user] Multiple files and other issues (part 2) Marco Bresciani wrote: > Ceki Gulcu ha scritto: >> The configuraition file looks good. Can you send a few lines of logging >> output in WebEML.log which should be in NEtO.log? > > Sure... tomorrow. ;-) Were you able to solve the issue? -- 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 -------------------------------------------------------------------- myhosting.com - Premium Microsoft® Windows® and Linux web and application hosting - http://link.myhosting.com/myhosting

1 0

ContextSelector and getLogger
by Martin Burchard 11 Mar '09

11 Mar '09

Hello, I currently try to get SLF4J and Logback to work on IBM Lotus Domino Server 8.5. It's working. We need to do logging an a per Thread basis because we log into a Domino database. The Java object of a Domino database is based on a session object, and that can not exist over more then one thread. Okay, I created a simple ContextSelector: package de.pentos.domino.logging; import java.util.Arrays; import java.util.List; import ch.qos.logback.classic.LoggerContext; /** * @author Martin Burchard */ public class ContextSelector implements ch.qos.logback.classic.selector.ContextSelector { private final LoggerContext defaultContext; private static final ThreadLocal<LoggerContext> threadLocal = new ThreadLocal<LoggerContext>(); public ContextSelector(final LoggerContext context) { defaultContext = context; } public LoggerContext detachLoggerContext(final String loggerContextName) { return getLoggerContext(); } public List<String> getContextNames() { return Arrays.asList(getLoggerContext().getName()); } public LoggerContext getDefaultLoggerContext() { return defaultContext; } public LoggerContext getLoggerContext() { LoggerContext lc = threadLocal.get(); if (lc == null) { threadLocal.set(new LoggerContext()); } return threadLocal.get(); } public LoggerContext getLoggerContext(final String name) { if (getLoggerContext().getName().equals(name)) { return getLoggerContext(); } return null; } } As long as all Loggers are used like this: private Logger log = LoggerFactory.getLogger(DemoWebService.class); everything works fine, I get my logging. But also this is a common way to get my Logger: private static final Logger log = LoggerFactory.getLogger(DemoWebService.class); Because for WebServices and Servlets the VM is not terminated and these Logger Instance will live a long time without ever get refreshed. After the first run I don't see logging any more. How can I deal with external JARs like Apache HTTP Client and other that instantiate the loggers in a static way? Regards, Martin -- View this message in context: http://www.nabble.com/ContextSelector-and-getLogger-tp22352655p22352655.html Sent from the Logback User mailing list archive at Nabble.com.

3 13

Re: [logback-user] Multiple files and other issues
by m.bresciani＠email.it 06 Mar '09

06 Mar '09

Thanks, I've given a very brief look and seems interesting and anyway useful. So, except for MDC, now I have to filter the packages. These go to different files, right? i.e.: whole application (or unspecified packages) - myapp.log special.package.one - specialone.log special.package.two - specialtwo.log sub-app or external load - anotherlog.log and so on. Thanks, Marco Original Message: ----------------- From: Ceki Gulcu ceki(a)qos.ch Date: Fri, 06 Mar 2009 12:16:35 +0100 To: logback-user(a)qos.ch Subject: Re: [logback-user] Multiple files and other issues The type of separation is possible. However, it is a relatively advanced feature. I suggest that you start by using MDC and go from there. MDC will allow you to distinguish log entries from issued from different sessions. However, all the logs will still go to the same file. Documentation on MDC can be found at http://logback.qos.ch/manual/mdc.html Cheers, Marco Bresciani wrote: > Sorry, I was not clear. > What happens now, with the basic file, is: > > 1. I run my application; > 2. the file trace/WebEML is created; > 3. the application is running; > 4. I run another session of my application (i.e.: double click again); > 5. the same trace/WebEML file seems used. > > I'd like to have, for example, something like: > > trace/WebEML_111145.log for the first application session, ran at 11:11.45 > and > > trace/WebEML_111222.log for the secon application session, ran at 11:12.22 > > or something like that, in order to distinguish the two different logs. Is > it possible? > > Thanks, > > Marco > -- > Caselle da 1GB, trasmetti allegati fino a 3GB e in piu' IMAP, POP3 e SMTP > autenticato? GRATIS solo con Email.it: http://www.email.it/f > > Sponsor: > Blu American Express: gratuita a vita! > > Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=8697&d=20090306 > > > _______________________________________________ > Logback-user mailing list > Logback-user(a)qos.ch > http://qos.ch/mailman/listinfo/logback-user > -- 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 -------------------------------------------------------------------- mail2web.com - Microsoft® Exchange solutions from a leading provider - http://link.mail2web.com/Business/Exchange

3 2

Re: [logback-user] Multiple files and other issues
by Marco Bresciani 06 Mar '09

06 Mar '09

--------- Original Message -------- Da: logback users list <logback-user(a)qos.ch> To: logback users list <logback-user(a)qos.ch> Oggetto: Re: [logback-user] Multiple files and other issues Data: 06/03/09 10:59 > What do you mean by customization of the file according to application session? > Do you mean that the log file *name* should depend on some data found in the > session or do you mean that the data contained *within* the log file should > depend on data from the session? By the way, what is the data in the session? Is > it the user name? Sorry, I was not clear. What happens now, with the basic file, is: 1. I run my application; 2. the file trace/WebEML is created; 3. the application is running; 4. I run another session of my application (i.e.: double click again); 5. the same trace/WebEML file seems used. I'd like to have, for example, something like: trace/WebEML_111145.log for the first application session, ran at 11:11.45 and trace/WebEML_111222.log for the secon application session, ran at 11:12.22 or something like that, in order to distinguish the two different logs. Is it possible? Thanks, Marco -- Caselle da 1GB, trasmetti allegati fino a 3GB e in piu' IMAP, POP3 e SMTP autenticato? GRATIS solo con Email.it: http://www.email.it/f Sponsor: Blu American Express: gratuita a vita! Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=8697&d=20090306

2 1

Re: [logback-user] Multiple files and other issues
by Marco Bresciani 06 Mar '09

06 Mar '09

--------- Original Message -------- Da: logback users list <logback-user(a)qos.ch> To: logback users list <logback-user(a)qos.ch> Oggetto: Re: [logback-user] Multiple files and other issues Data: 06/03/09 09:42 > Let's start one problem at a time. Here is a simple config file. Try using it > and see how it goes. Will build up from there. Thanks! I've created the logback.xml file with some (very minor) modifications from yours: > <file>traces/MyApp</file> <file>trace/WebEML</file> and it obviously works... :-) WebEML is the name my product managers chose for my application... even if it has *nothing* to do with web... long story (or stupid PMs, as you prefer). > If you can run the above correctly, we'll add more functionality one step at a > time. Starting from this, I think that the next step should be the customization of the file according to application session... then I'll think about levels and packages "split" on other files. Thanks again, Marco -- Caselle da 1GB, trasmetti allegati fino a 3GB e in piu' IMAP, POP3 e SMTP autenticato? GRATIS solo con Email.it: http://www.email.it/f Sponsor: I Mostri Oggi: scopri i vizi degli italiani Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=8792&d=20090306

2 1

Incorrect thread name in plugin console
by Raccoonwao 06 Mar '09

06 Mar '09

Hi everybody, I am using the eclipse logback console but found that [%thread] gives me the wrong thread name. It shows something like [Thread-70] rather than the real thread name in my application. Here is the logging statement private static final Logger logger = LoggerFactory.getLogger(TestView.class); .... logger.error("testing test ing"); .... I noticed there is a code in the ch.qos.logback.eclipse.reciever.SocketNode (line 59), which I copied here. try { while (true) { // read an event from the wire event = (LoggingEvent) ois.readObject(); // trick to keep the original thread name event.getThreadName(); // add it to the manager's LoggingEvent list LoggingEventManager.getManager().addLoggingEvent(event); } The comment said it is a trick to keep the original thread name. It seems not working anymore, is it? Or, am I missing something? Also, I have fired a bug here http://jira.qos.ch/browse/CONSPLUG-18 Thanks a lot Leung Wang Hei Yahoo!香港提供網上安全攻略，教你如何防範黑客! 請前往 http://hk.promo.yahoo.com/security/ 了解更多!

1 0

Multiple files and other issues
by Marco Bresciani 06 Mar '09

06 Mar '09

Hello all, I've just began using Logback and it is sooo good! :-) I'm still a newbie so for my attempts I'm using the online wizard and then trying to adapting and customizing it by hand, when needed, in order to find the correct configuration for my needs (many packages, many classes, different needs and logs levels, ...). I've reached a sort of nirvana by simply using the wizard without any customization and no other "strange things". I've read the manual again and again but I'm still having some problems, anyway. :-( (I'm going to feel the dark side of the newbies...) Could anyone please help? (At the end of the email, an example logback.xml I've made with the wizard) 1. I've tried to use HTML file format, even with a very simple/basic configuration, but no output has been produced; 2. I'm getting crazy trying to have a customizable/variable file name. If two instances of my application run; I need to have two logs. I.e.: first instance being ran at 10.30, second instance being ran at 11.04 then the log files should be something like logs/MyApp(a)10.30.45.log and logs/MyApp(a)11.04.32.log. I really need this and I'm getting crazy... Please help! 3. I'm still having a bit of troubles in splitting the logs of specific parts or packages or sub-applications, through different log files. I.e.: logs/MyApp(a)10.30.45.log and logs/MyApp_SpecialPackage(a)10.30.46.log and so on. Is the XML made by the wizard correct? Really really thanks in advance for any help anyone could give me, Marco This is an example of what I've done... many attempts... <?xml version="1.0" encoding="UTF-8"?> <configuration> <appender class="ch.qos.logback.core.FileAppender" name="my.special.package.logger.thingFileAppender"> <file>traces/SpecialPackage</file> <append>true</append> <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>error</level> </filter> <layout class="ch.qos.logback.classic.PatternLayout"> <pattern>%d{yyyy-MM-dd HH:mm:ss},%p,%c,%t,%C{1},%M %m%n</pattern> </layout> </appender> <appender class="ch.qos.logback.core.FileAppender" name="RootFileAppender"> <file>traces/MyApp</file> <append>false</append> <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>error</level> </filter> <layout class="ch.qos.logback.classic.PatternLayout"> <pattern>%d{yyyy-MM-dd HH:mm:ss},%p,%c,%F,%C{1} %m%n</pattern> </layout> </appender> <logger additivity="false" name="my.special.package.logger.thing"> <level value="error"/> <appender-ref ref="my.special.package.logger.thingFileAppender"/> </logger> <root> <level value="debug"/> <appender-ref ref="RootFileAppender"/> </root> </configuration>

2 1