- logback-user - mailman3.qos.ch

Inconsistency in printing Throwable instances?
by Abraham Lin 16 Jul '12

16 Jul '12

Hi, In comparing the outputs of Throwable#printStackTrace and logback, I found an inconsistency in how the Throwable instances are printed. While the former delegates to the Throwable instance's #toString method, the latter (partially) re-implements the default implementation in Throwable, which means that data contained in the #toString methods of Throwable subclasses is discarded. While this is easy to work around in my own code, there is still a problem when working with third-party libraries. Is there a configuration option that would allow me to specify my own IThrowableProxy implementation? (I couldn't find any pages describing the extension points and how to activate them.) Or would it be more appropriate to modify the ThrowableProxyUtil class so that it behaves similarly to #printStackTrace? Any ideas would be greatly appreciated. Thanks in advance! -Abraham

2 4

logging_event_property
by Odelya Holiday 11 Jul '12

11 Jul '12

Hi! What is the goal of logging_event_property table? Is there a way to remove it or get rid of it? Thanks -- Odelya

3 7

Re: [logback-user] Custom Logger for logging custom object?
by Adam Brightwell 09 Jul '12

09 Jul '12

Hey Andrzej, Thanks for the suggestion. I agree that this would be a straight forward solution. Unfortunately, overriding the toString() method will not work as the format of the log message must be configurable. Much in the same way that you can configure the format of a log message using the PatternLayout. For obvious reasons, I believe the format and the message data should be independent of each other. Thanks again, I appreciate the quick response. Thanks, Adam From: Andrzej Zadorozny <andrzej.zadorozny(a)gmail.com<mailto:andrzej.zadorozny@gmail.com>> Date: Friday, July 6, 2012 10:20 PM To: Adam Brightwell <abrightwell(a)lce.com<mailto:abrightwell@lce.com>> Subject: Re: [logback-user] Custom Logger for logging custom object? Hi Adam, If you could have the POJOs implement their own toString() method (if it's possible in your situation), I think that would be a straight forward solution. CheerZ! :) On Fri, Jul 6, 2012 at 7:15 PM, Adam Brightwell <abrightwell(a)lce.com<mailto:abrightwell@lce.com>> wrote: Hey All, I have an interesting logging requirement in front of me. I am required to log application specific information that is contained within a custom POJO. The developers will create and fill these POJO's with the appropriate information when a logging "event" takes place. The hope was that it could then be passed off to our logging system and it would know what to do with it. However, the obvious problem is that Logger can't be overridden to allow the overloading of the info, warn, error, etc. methods to receive the custom POJO. I have considered simply implementing the "Delegation Pattern" implementing the slf4j Logger interface and wrapping the logback Logger which would allow me to simply overload the necessary methods. I was curious what the communities thoughts might be on this potential solution. Are there other recommendations that might work better for my purposes? Any help, recommendations or guidance would be greatly appreciated. Thanks, Adam _______________________________________________ Logback-user mailing list Logback-user(a)qos.ch<mailto:Logback-user@qos.ch> http://mailman.qos.ch/mailman/listinfo/logback-user -- Andrzej Zadorozny

2 1

Java programmatic configurations
by Martinus Martinus 09 Jul '12

09 Jul '12

Hi, What is the equivalent programmatical java code for below logback.xml configuration : <configuration> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">  <encoder> <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger - %msg%n</pattern> </encoder> </appender> <appender name="SYSLOG" class="ch.qos.logback.classic.net.SyslogAppender"> * <syslogHost>myhost</syslogHost>* * <facility>USER</facility>* * <suffixPattern>[%thread] %logger *%msg</suffixPattern> </appender> <root level="debug"> <appender-ref ref="SYSLOG"/> <appender-ref ref="STDOUT"/> </root> </configuration> Thanks.

2 2

AUTO: Manfred Kuhlmann is out of office. (Rückkehr am 30.07.2012)
by manfred.kuhlmann＠steria-mummert.de 07 Jul '12

07 Jul '12

Ich werde ab dem 06.07.2012 nicht im Büro sein. Ich kehre zurück am 30.07.2012. I will be out of the office starting 06.07.2012. I will be back on 30.07.2012. Ihre Nachricht werde ich nach meiner Rückkehr beantworten. Mit freundlichen Grüßen Manfred Kuhlmann Hinweis: Dies ist eine automatische Antwort auf Ihre Nachricht " [logback-user] Custom Logger for logging custom object?" gesendet am 07.07.2012 03:15:50. 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 pro Seite. Diese Nachricht kann vertrauliche Informationen enthalten und ist allein für den Adressaten bestimmt. Wenn Sie nicht der rechtmäßige Empfänger sind, sind 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 E-Mail zu löschen. Der Inhalt von E-Mails innerhalb des Netzwerks kann überprüft werden, um die Übereinstimmung mit den geltenden Firmenrichtlinien und Vorgehensweisen 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 können. This e-mail 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 e-mail in any way. Please notify the sender and delete the e-mail and any copies of it. The content of e-mails within our network may be monitored to ensure compliance with company policies and procedures. E-mails can be alterated by third parties in transit. Therefore any e-mail is susceptible to alteration and its integrity cannot be assured.

1 0

Custom Logger for logging custom object?
by Adam Brightwell 07 Jul '12

07 Jul '12

Hey All, I have an interesting logging requirement in front of me. I am required to log application specific information that is contained within a custom POJO. The developers will create and fill these POJO's with the appropriate information when a logging "event" takes place. The hope was that it could then be passed off to our logging system and it would know what to do with it. However, the obvious problem is that Logger can't be overridden to allow the overloading of the info, warn, error, etc. methods to receive the custom POJO. I have considered simply implementing the "Delegation Pattern" implementing the slf4j Logger interface and wrapping the logback Logger which would allow me to simply overload the necessary methods. I was curious what the communities thoughts might be on this potential solution. Are there other recommendations that might work better for my purposes? Any help, recommendations or guidance would be greatly appreciated. Thanks, Adam

1 0

logback cannot load configuration from a jar running as an applet
by Andriy Tylychko 06 Jul '12

06 Jul '12

I have a weird issue with logback configuration. My project is packet into jar files, server side and client side. Client side is run as an applet in a browser. Server side works fine, but client cannot find its configuration file (I believe so). My custom configuration doesn't work. I set log level to INFO in the configuration file logback.xml which is in the root folder of the jar, but still see DEBUG logs in Java console. Logback's internal info: 11:20:08,924 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback.groovy] 11:20:08,982 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml] 11:20:09,042 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback.xml] Seems like this is somehow related with my applet, or any applet. More info here: http://stackoverflow.com/questions/11343311/logback-configuration-is-not-se… Please help. Thank you, Andy

1 0

rolling log files
by J.V. 05 Jul '12

05 Jul '12

I want to set 'append=false' but have each log file created have a timestamp of the creation in the name so as to not overwrite previous log files. How is this accomplished (if possible at all)? thanks J.V.

2 1

multiple log files question
by J.V. 05 Jul '12

05 Jul '12

I want to start a new project with logback and leave log4j behind and see how it goes. We have an upgrade process for which I want to create multiple log files in my application: A summary log file A debug log file A cleanup log file An error log file Summary: <= will contain info and errors Debug: <= will contain info, warnings, errors, debug - everything, the kitchen sink Cleanup <= will contain statements (info) about which rows from a database were deleted as a result of the cleanup (these could be spread throughout the program in many class files) Error <= will contain warnings, errors only I am trying to put together a logback.groovy that would do this and test with some Java classes but am having some difficulty. Is there a way I can configure this in a logback.groovy and then have each of the statements needed go to the specific files created? Essentially: summary.log <= info & errors debug.log <= all levels cleanup.log <= only info statements about which rows deleted (this one is tricky) error.log <= warnings, error statements only thanks J.V.

1 0

Additional logback config
by Christian Lipp 05 Jul '12

05 Jul '12

Hello! I have a web application running under Tomcat with uses Logging separation as described here: http://logback.qos.ch/manual/loggingSeparation.html#ContextJNDISelector This means that logback jars are located under ${catalina.home}\lib. For the build I use maven and perform also a integration test with the maven-failsafe-plugin and the tomcat-maven-plugin. The tomcat-maven-plugin has the logback jars as dependencies, but I do not know how to provide a logback.xml. Of course I could use a ServletContextListener to distinguish programmatically between development and production environment. What are best practices to separate development logging, integration test logging and production logging when development logging should use the config inside the war and production logging should use the logging set up by the operational team in the Tomcat? Is it possible to determine if the logging infrastructure is set up or not? I could use this information in a ServletContextListener to force a new initialisation. Is it possible to tell logback to use the config file in WEB-INF\classes even if the logback jars are located under ${catalina.home}\lib? Kind regards, CL

1 1