- logback-user - mailman3.qos.ch

Eclipse console plugin
by Matthias Kretschmar 08 Apr '10

08 Apr '10

Hi, on the download page I read about the Eclipse Console Plugin. Unfortunately I'm using Logback 0.9.20. So I can't use the plugin. I've been waiting for the plugin for a few months, but nothing happend. Is there a plan of QOS for updating the version, or is it possible, that anybody else does this? -- Matthias

2 2

SMTPAppender with multiple evaluators
by Naor Yuval 07 Apr '10

07 Apr '10

Hi. I am looking to implement an SmtpAppender that will allow to specify "delivery rules" based on the evaluation of the error-log. For example, for some specific exceptions we wish to send the first occurrence, then buffer the rest and send a digest every hour. For other specific exception types we wish to send each log immediately What is the recommended way to implement such behavior? Could appenders be chained somehow to accomplish this? Thanks, Naor

2 2

logback generated a lot of file with *.tmp
by Ted Meng 03 Apr '10

03 Apr '10

Hello: when the log needs to be rotated often, many temporary files like *.tmp are being produced and left there forever. I saw the following mailing thread and did not see futher info http://marc.info/?l=logback-user&m=125310684231076&w=2 How could I avoid this situation within logback. Thanks -Ted

2 1

Release of logback v0.9.20
by Ceki Gülcü 01 Apr '10

01 Apr '10

Hello all, I am happy to announce the immediate availability of logback version 0.9.20. In addition to bug fixes, this version introduces conditional processing of configuration files. Please refer to the the news page for precise details. http://logback.qos.ch/news.html You can download logback, including full source code, class files and documentation on our download page, shown below. http://logback.qos.ch/download.html You can receive logback related announcements by subscribing to the QOS.ch announce mailing list. To subscribe to QOS.ch announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/announce -- Ceki

1 0

Re: [logback-user] Standalone instance with multiple log4j setting
by Ceki Gülcü 01 Apr '10

01 Apr '10

On 01/04/2010 12:41 PM, WM YEOH wrote: > Hi Ceki, > > Thank you for the guidance. > > I think I better start all over again what was the actual problem to give > you a better picture. > > I am currently upgrading the sun one apps server from 7.1 to 9.1 (in UNIX > platform), common-logging.jar, jakarta-log4j-1.2.6.jar and log4j-1.2.15.jar > are currently specified in the server classpath. The logging problem > occurred after upgraded to 9.1. You should not have both jakarta-log4j-1.2.6.jar and log4j-1.2.15.jar on the server's class path. Pick one and only one. > I have an EAR file containing few jars (EJB involved) and a war file > deploying in a standalone instance. I have another war file deployed within > the same instance, meaning there are 2 apps running in one instance. When > the instance startup, there are suppose to have 2 log files, for instance > A.log and B.log. However, all the loggers only written in a single log, take > A.log as an example. Both apps have their own initServlet to load the log4j > configuration files. > > I need some answers from you in order to clear my doubts, > > - is logback my only solution? No, logback is not your only solution. You could change the problem setting by using non-static logger references in your EJB classes. With the simplified problem you could stick with log4j. Having said that logback is the only platform that deals with the logging separation problem for shared classes with static loggers. Given that the rest of your post is logback related, I posted my full answer on the logback-user mailing list. If you wish to pursue the logback-based solution, then please continue the discussion there. > - can I used log4j-1.2.15 instead of slf4j-api-1.5.11? You could either migrate your source code from log4j to slf4j with the slf4j-migrator (http://slf4j.org/migrator.html) or replace log4j.jar with log4j-over-slf4j as described in http://slf4j.org/legacy.html#log4j-over-slf4j. > - I am not too sure how logback.xml is been read, initServlet triggered > to lookup the xml file or no sevlet needed only specified in web.xml? Once installed ContextJNDISelector will determine whether the current logger context has been initialized and if not will read in the configuration as appropriate for the current context. The current context value is read from JNDI according to the "logback/context-name" env-entry you put in your web-app's web.xml file. This is described in http://logback.qos.ch/manual/loggingSeparation.html. > - what should be the value for<env-entry-value>, just the xml file name > or should I include the path as well like /WEB-INF/classes/xml/A1.xml Good question. The value of "logback/configuration-resource" env-entry is looked up as a *resource*. So if you place A1.xml under the /WEB-INF/classes/xml/ folder, you would need to specify the resource name "xml/A1.xml". > - by looking at the logback-starwars project, it looks very simple. And I > assume there neither to add -Dlogback.ContextSelector=JNDI nor > Dlogback.ContextSelector=myPackage.myContextSelector in system property? If you wish to install the ContextJNDISelector, just set the "logback.ContextSelector" system property to "JNDI". > - is "myPackage.myContextSelector" means custom context selector written > by me? Yes. > Appreciate if you can help me to understand more about the logback > concept and how can I solve the problem. Hope to hear from you soon. > > Thank you. You are welcome. -- Ceki

1 0

Logging tool for JDBC
by Joern Huxhorn 31 Mar '10

31 Mar '10

I've just seen this this post on theserverside.com. It looks quite interesting and is using SLF4J as the logging framework. http://code.google.com/p/jdbcdslog/ http://www.theserverside.com/discussions/thread.tss?thread_id=59817 Cheers, Joern.

2 1

AUTO: Manfred Kuhlmann is out of office. (Rückkehr am 06.04.2010)
by manfred.kuhlmann＠steria-mummert.de 31 Mar '10

31 Mar '10

Ich werde ab dem 29.03.2010 nicht im Büro sein. Ich kehre zurück am 06.04.2010. I will be out of the office starting 29.03.2010. I will be back on 06.04.2010. Ihre Nachricht werde ich nach meiner Rückkehr beantworten. I will answer your message after my return. Bitte Ihre Ansprechpartner in der Mitarbeiterdatenbank unter dem Reiter 'Abwesenheitsvertreter' eingeben (s.a. Hilfe-Button). Mit freundlichen Grüßen Best regards Manfred Kuhlmann Hinweis: Dies ist eine automatische Antwort auf Ihre Nachricht " [logback-user] Logging tool for JDBC" gesendet am 31.03.2010 11:52:02. Diese ist die einzige Benachrichtigung, die Sie empfangen werden, während diese Person abwesend ist. Steria Mummert Consulting AG Vorsitzender des Aufsichtsrates: Jürgen Sponnagel - Vorstand: Oliver Nazet (Vors.), Dr. Reinhard Liedl, Dr. Fritz Moser Gesellschaftssitz: Hamburg - HR B 61 116 Amtsgericht Hamburg - USt-ID-Nr.: DE118671351 Bitte denken Sie an Ihre Verantwortung gegenüber der Umwelt: Jede ausgedruckte E-Mail verursacht ca. 0,3 Gramm CO2. Diese Nachricht kann vertrauliche Informationen enthalten und ist allein für den Adressaten bestimmt. Wenn Sie nicht der rechtmäßige Empfänger sind, ist der Zugriff, die Weiterleitung, das Kopieren, die Veröffentlichung oder anderweitige Verwendung des Inhalts untersagt. In diesem Fall bitten wir Sie den Absender unverzüglich zu informieren und diese E-Mail sowie sämtliche Kopien dieser Email zu löschen. Der Inhalt von E-Mails innerhalb des Netzwerks kann überprüft werden, um die Übereinstimmung mit den geltenden Firmenrichtlinien und Vorgehens-weisen zu gewährleisten. E-Mails können auf dem Transportweg von Dritten verändert werden, so dass deren Vollständigkeit und Echtheit nicht garantiert werden kann. This Email communication may contain confidential information and is intended only for the recipient. If you are not the intended recipient you are not allowed to read, copy, distribute, publicize or use the content of this Email in any way. Please notify the sender and delete the Email and any copies of it. The content of Emails within our network may be monitored to ensure compliance with company policies and procedures. Emails can be alterated by third parties in transit. Therefore any Email is susceptible to alteration and its integrity cannot be assured.

1 0

resend. logback include file can not be found
by Ted Meng 26 Mar '10

26 Mar '10

Hi: I put an include directive in my logback.xml <configuration> <include file="includedConfig.xml" /> </configuration> the "includedConfig.xml" is in the same directory (classpath) as the logback.xml file itself. But logback runtime keeps saying [java] 03:21:41,533 |-ERROR in ch.qos.logback.core.joran.action.IncludeAction - File [includedConfig.xml] does not exist. java.io.FileNotFoundException: logback.xml (The system cannot find the file specified) Using a absolute path is not a choice here so I wonder what would be the best way to do this or maybe I misunderstand something. I'd assume logback program would know the location of logback.xml so it would use it as the reference point to figure out any relative path. Thanks -Ted

3 7

Lilith 0.9.38 has been released!
by Joern Huxhorn 26 Mar '10

26 Mar '10

This release features more comfortable filtering of events and adds the ability to directly write Lilith logfiles using Logback. Please see the appropriate section in the help for more info. - Added help about using Lilith encoders in FileAppender. - Added detection of outdated index files and the option to reindex a log file in that case. This is helpful while reopening log files created by a FileAppender. - Added new modules de.huxhorn.lilith.logback.encoder.classic and de.huxhorn.lilith.logback.encoder.access to support writing of Lilith logfiles using Logback FileAppender. Thanks to Ceki for supporting this! - Added some more tips. - Added shortcut for "Close all" action. - Views aren't opened anymore in case of connection closed for black- or not whitelisted sources. This was reported by Vlad Satanovski. - Added the ability to clear a filtered view. Doing this clears the original view and resets the filtered view. This was suggested by Joe. - Moved BufferTableModel to new module sulky-buffers-table. - Moved RowBasedTableModel and PersistentTableColumnModel to module sulky-swing. - Implemented the workaround for Apple Problem ID #7240026 suggested by GalaJon. Thanks a lot! See http://bit.ly/5vF5M2 - Of-by-one error in message renderer [+x lines]. - Lilith log is now showing uncaught exceptions as errors. - Added "Uncaught Exception" debug action. - The find panel has been heavily refactored. Instead of a text-field it now features a combobox containing the previous 15 searches that were used for filtered views. Additionally, there's a new filter type "Named" that populates the combobox with named/saved conditions. Similarly, selecting "Level>=" populates the combobox with the correct values from TRACE to ERROR. The comboboxes, both filter type selection and filter text, feature autocompletion of entered text. This was suggested by Joe. - updated: SLF4J 1.5.11, Logback 0.9.19, Groovy 1.7.0, Protobuf 2.3.0 Download it now! http://sourceforge.net/projects/lilith/files/lilith/0.9.38 Cheers, Joern.

1 0

ConsoleAppender/FileAppender encoding
by Matthieu Guamis 25 Mar '10

25 Mar '10

Hi, It seems that element "encoding" is no more recognized in Console/FileAppender so maybe I missed something (no more reference in documentation) but I did not find what :( Here is my (new) configuration (logback 0.9.19) <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <encoding>UTF-8</encoding> <encoder> <pattern>%d %t [%-5level] - %-40class{40} - %msg%n</pattern> </encoder> </appender> And the corresponding output at runtime: [...] 15:58:29,127 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender] 15:58:29,146 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [STDOUT] 15:58:29,226 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@7:13 - no applicable action for [encoding], current pattern is [[configuration][appender][encoding]] 15:58:29,230 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Pushing component [encoder] on top of the object stack. 15:58:29,403 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting additivity of logger [org.barracudamvc] to true 15:58:29,403 |-INFO in ch.qos.logback.classic.joran.action.LevelAction - org.barracudamvc level set to WARN 15:58:29,403 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STDOUT] to Logger[org.barracudamvc] [...] Any suggestion on what could be wrong? Thanks -- *Matthieu Guamis* *Logo Axège <http://www.axege.com/>* /Axège// 23,rue Saint-Simon 63000 Clermont-Ferrand/ Tél: +33 (0)4 63 05 95 40 Fax: +33 (0)4.73.70.65.29 Email: matthieu.guamis(a)axege.com <mailto:matthieu.guamis@axege.com>

2 3