July 2012 - logback-user - mailman3.qos.ch

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

Java programmatic configurations
by Martinus Martinus 05 Jul '12

05 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.

1 0

Log method name and line number only for exceptions
by lopardo . 04 Jul '12

04 Jul '12

Hi. Is it possible to log method name and line number only for exceptions? Or set a different pattern, but only for exceptions? That way I could log more info, even if it's slower to process, for some exceptions. Thanks. Regards, lopardo.

2 1

Java programmatic configurations
by Martinus Martinus 04 Jul '12

04 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.

1 0

DuplicateMessageFilter
by the KD 02 Jul '12

02 Jul '12

I have a situation where we need to limit the number of errors logged and sent to production support. I first thought this filter might be useful, but after analyzing our need, we feel it is not useful. For example, if I limit it to 3 times of repetition, how do we now if the error was fixed or it simply was not thrown due to the filtering? My suggestion is, it can be more useful for practical purpose if there can be some "time duration" parameter in it where one specifies, for example, 1 hr, or 1 minute, to indicate that the error cannot be repeated this many times within certain duration. Kevin -- View this message in context: http://old.nabble.com/DuplicateMessageFilter-tp34083524p34083524.html Sent from the Logback User mailing list archive at Nabble.com.

1 0