- logback-user - mailman3.qos.ch

Customize how some objects are "printed"
by Blaise Gervais 19 Jun '12

19 Jun '12

Hi everyone, We are used to log the current user. But the current user is a complex object with a ugly "toString()" who print many unuseful informations with new lines. And, of course, we can't override that. To have clean logs, we have to walk into the user object structure until relevant informations and deal with many possibles null pointers. My question is : Is it a way to register something usable by SLF4J to render an object to a String ? Something like : <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> *<renderer class="com.our.company.logging.UserContextRenderer" **/>* </appender>

1 0

logback-1.0.3 - Rolled over log file was overwritten instead of incremented
by Stephan Olbertz 19 Jun '12

19 Jun '12

Hi, as it says in the title, I use logback 1.0.3 and I encountered a problem last night. My application was started in two separate instances and it was logging alright. I have it set up to do a rollover on midnight and when the file reaches a certain size. On 00:38 a rollover happened initiated by one of the instances to file " osail.2012-06-18.0.log"and I assume it went through alright. But, on 00:58 the second instance was done and it also initiated a rollover and it also rolled over to file "osail.2012-06-18.0.log". Overwriting the first file. I assumed it would have switched to file "osail.2012-06-18.1.log" but that was not the case? Can any body help me out, here? For reference, this is my logback.xml: <configuration debug="true"> <property name="LOGS.DIR" value= "/nfs/us08/rm_info/protex_scan/logs" /> <appender name="FILE" class= "ch.qos.logback.core.rolling.RollingFileAppender"> <file>${LOGS.DIR}/osail.log</file>  <append>true</append> <rollingPolicy class= "ch.qos.logback.core.rolling.TimeBasedRollingPolicy">  <fileNamePattern>${LOGS.DIR}/osail.%d{yyyy-MM-dd}.%i.log</ fileNamePattern> <timeBasedFileNamingAndTriggeringPolicy class= "ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP">  <maxFileSize>3MB</maxFileSize> </timeBasedFileNamingAndTriggeringPolicy>  <maxHistory>5</maxHistory> </rollingPolicy>  <encoder>  <pattern>%d [%thread] %-5level %logger{36} - %msg%n</pattern> </encoder> </appender> <root level="DEBUG"> <appender-ref ref="FILE" /> </root> </configuration> Best regards, Stephan The information included in this e-mail and any files transmitted with it is strictly confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately by e-mail and delete this e-mail as well as any attachment from your system. If you are not the intended recipient you are not authorized to use and/or copy this message and/or attachment and/or disclose the contents to any other person.

1 0

more INFO logs messages from StatusListeners after update
by fed 18 Jun '12

18 Jun '12

Hi, i was using logback 1.0.3 then now i updated it to 1.0.6, on my groovy configuration file i have statusListener(OnConsoleStatusListener). Now with the same configuration i get a lot of INFO messages about logback status at the start of my application for example: 23:49:48,015 |-INFO in ch.qos.logback.classic.gaffer.ConfigurationDelegate@2b323e - Added status listener of type [ch.qos.logback.core.status.OnConsoleStatusListener] 23:49:48,062 |-INFO in ch.qos.logback.classic.gaffer.ConfigurationDelegate@2b323e - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender] 23:49:48,062 |-INFO in ch.qos.logback.classic.gaffer.ConfigurationDelegate@2b323e - Naming appender as [TRACE_FILE] 23:49:48,218 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - No compression will be used ... more they are not a problem, i see them only at start, but i am wondering why i see them now after the update and not before when i was using 1.0.3, what is changed? If it is possible i would like to see only error/warn messages from logback status Thanks Regards.

2 1

configuration through JNDI
by bjorn rohde jensen 18 Jun '12

18 Jun '12

Hi guys, I recently switched to logback, and im trying to use JNDI to configure logback for webapps running in tomcat 6. What i want to do is configure logging for each webapp using a different configuration file for each tomcat context. The logback configurations must be external to the wars and to the tomcat installation. Furthermore i cant rely on environment variables or -D options to the tomcat. The only solution, i have come up with so far is to pack a skeleton logback configuration file in the war, which uses logbacks JNDI and include mechanisms to locate and include a file containing the real configuration like so: <configuration scan="true" scanPeriod="5 minutes"> <insertFromJNDI env-entry-name="java:comp/env/appName/logback" as="logbackConfiguration"/> <include url="${logbackConfiguration}"/> </configuration> While this does work, i would prefer being able to lookup the full configuration directly. Is there a way to do this, or could one be added? Yours sincerely, Bjorn R. Jensen

2 2

SNMP appender for logback
by ofer lilian 18 Jun '12

18 Jun '12

Hi, Is there any SNMP appender for logback ?

1 0

SNMP appender
by ofer lilian 18 Jun '12

18 Jun '12

Hi, Is there any SNMP appender for logback ?

1 0

JNDI DBAppender with WebLogic pool connection - Cannot call commit when using distributed transactions
by Smith, Larry (ECS - Enterprise Cloud Service) 18 Jun '12

18 Jun '12

Using Logback classic 1.0.6 (slf4j 1.6.5) Running on a Weblogic server 10.3.5. I just added the DBAppender and have some unusual errors that get generated. My append statement works fine and it does log entries to the database: <appender name="DataBase" class="ch.qos.logback.classic.db.DBAppender"> <connectionSource class="ch.qos.logback.core.db.JNDIConnectionSource"> <param name="jndiLocation" value="UCS_DS." /> </connectionSource> </appender> Weblogic reports the following about the datasource creation (This pool on my local machine starts at 6 and grows by 2 up to 40 connections): <BEA-001177> <Creating Connection Pool named UCS_DS, URL = jdbc:oracle:thin:@localhost:1521:XE, Properties = user=logback;.> <BEA-000626> <Free resources in pool "UCS_DS" will be tested every "120" seconds.> <BEA-001066> <Delaying 6 seconds before making a UCS_DS pool connection.> <BEA-001516> <Connection Pool "UCS_DS" connected to Database: "Oracle", Version: "Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production".> <BEA-001517> <Connection Pool "UCS_DS" using Driver: "Oracle JDBC driver", Version: "11.2.0.2.0".> <BEA-001066> <Delaying 6 seconds before making a UCS_DS pool connection.> <BEA-001066> <Delaying 6 seconds before making a UCS_DS pool connection.> <BEA-001066> <Delaying 6 seconds before making a UCS_DS pool connection.> <BEA-001066> <Delaying 6 seconds before making a UCS_DS pool connection.> <BEA-001066> <Delaying 6 seconds before making a UCS_DS pool connection.> <BEA-000628> <Created "6" resources for pool "UCS_DS", out of which "6" are available and "0" are unavailable.> <BEA-001124> <Created Connection Pool named UCS_DS.> <BEA-001174> <Creating Data Source named UCS_DS, JNDI Name = UCS_DS.> <BEA-001512> <Data Source UCS_DS has been successfully created.> But this error is thrown quite frequently. 20:38:56,700 |-ERROR in ch.qos.logback.classic.db.DBAppender[DataBase] - problem appending event java.sql.SQLException: Cannot call commit when using distributed transactions at java.sql.SQLException: Cannot call commit when using distributed transactions at at weblogic.jdbc.wrapper.JTAConnection.commit(JTAConnection.java:355) at at ch.qos.logback.core.db.DBAppenderBase.append(DBAppenderBase.java:116) at at ch.qos.logback.core.UnsynchronizedAppenderBase.doAppend(UnsynchronizedAppenderBase.java:88) at at ch.qos.logback.core.spi.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:48) at at ch.qos.logback.classic.Logger.appendLoopOnAppenders(Logger.java:282) at at ch.qos.logback.classic.Logger.callAppenders(Logger.java:269) at at ch.qos.logback.classic.Logger.buildLoggingEventAndAppend(Logger.java:470) at at ch.qos.logback.classic.Logger.filterAndLog_0_Or3Plus(Logger.java:424) at at ch.qos.logback.classic.Logger.info(Logger.java:628) And I also see this: <BEA-001153> <Forcibly releasing inactive connection "[weblogic.jdbc.wrapper.JTAConnection_weblogic_jdbc_wrapper_XAConnection_oracle_jdbc_driver_LogicalConnection-UCS_DS-2, oracle.jdbc.driver.LogicalConnection@11d5e99]" back into the connection pool "UCS_DS", currently reserved by: java.lang.Exception at weblogic.jdbc.common.internal.ConnectionEnv.setup(ConnectionEnv.java:325) at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:363) at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:329) at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:417) at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:324) at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:94) at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:63) at weblogic.jdbc.jta.DataSource.getXAConnectionFromPool(DataSource.java:1677) at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1475) at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:446) at weblogic.jdbc.jta.DataSource.connect(DataSource.java:403) at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:364) at ch.qos.logback.core.db.JNDIConnectionSource.getConnection(JNDIConnectionSource.java:63) at ch.qos.logback.core.db.ConnectionSourceBase.discoverConnectionProperties(ConnectionSourceBase.java:47) at ch.qos.logback.core.db.JNDIConnectionSource.start(JNDIConnectionSource.java:50) at ch.qos.logback.core.joran.action.NestedComplexPropertyIA.end(NestedComplexPropertyIA.java:167) at ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:318) at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:197) at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:183) at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:62) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:147) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:133) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:96) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:55) at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:75) at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:148) at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:84) at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:54) at org.slf4j.LoggerFactory.bind(LoggerFactory.java:128) at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:108) at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:279) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:252) at org.apache.commons.logging.impl.SLF4JLogFactory.getInstance(SLF4JLogFactory.java:156) at org.apache.commons.logging.impl.SLF4JLogFactory.getInstance(SLF4JLogFactory.java:132) at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:645) at org.displaytag.tags.TableTag.<clinit>(TableTag.java:104) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:169) at org.displaytag.tags.TableTagBeanInfo.class$(TableTagBeanInfo.java:42) at org.displaytag.tags.TableTagBeanInfo.getPropertyDescriptors(TableTagBeanInfo.java:41) at java.beans.Introspector.getTargetPropertyInfo(Introspector.java:501) at java.beans.Introspector.getBeanInfo(Introspector.java:410) at java.beans.Introspector.getBeanInfo(Introspector.java:232) at java.beans.Introspector.<init>(Introspector.java:389) at java.beans.Introspector.getBeanInfo(Introspector.java:232) at java.beans.Introspector.getBeanInfo(Introspector.java:218) at weblogic.jsp.internal.jsp.tag.TagInfoEx.getPropertyDescriptorSetterTypes(TagInfoEx.java:554) at weblogic.jsp.internal.jsp.tag.TagInfoEx.getSetterTypes(TagInfoEx.java:499) at weblogic.jsp.internal.jsp.tag.TagInfoEx.initAttributeTypes(TagInfoEx.java:395) at weblogic.jsp.internal.jsp.JspActionChecker.checkActionStart(JspActionChecker.java:287) at weblogic.jsp.internal.jsp.JspActionChecker.checkActions(JspActionChecker.java:214) at weblogic.jsp.internal.jsp.JspActionChecker.checkActions(JspActionChecker.java:228) at weblogic.jsp.internal.jsp.JspActionChecker.check(JspActionChecker.java:150) at weblogic.jsp.internal.jsp.JspCheckContext.check(JspCheckContext.java:67) at weblogic.jsp.internal.jsp.JspAnalyzer.check(JspAnalyzer.java:57) at weblogic.jsp.internal.ProxySourceFile._check(ProxySourceFile.java:136) at weblogic.jsp.internal.SourceFile.masterCheck(SourceFile.java:762) at weblogic.jsp.internal.SourceFile.check(SourceFile.java:314) at weblogic.jsp.internal.SourceFile.check(SourceFile.java:335) at weblogic.jsp.internal.ProxySourceFile.codeGen(ProxySourceFile.java:224) at weblogic.jsp.internal.SourceFile.codeGen(SourceFile.java:327) at weblogic.jsp.internal.client.ClientUtilsImpl$CodeGenJob.run(ClientUtilsImpl.java:599) at weblogic.jsp.internal.client.Job.performJob(Job.java:83) at weblogic.jsp.internal.client.ThreadPool$WorkerThread.run(ThreadPool.java:217) .> So my questions are: 1. Is there a way to not throw the error? 2. What type of performance impact can this cause? Larry Smith

2 1

Split logs to different files by MDC?
by Yura Levandovskyy 15 Jun '12

15 Jun '12

Hello I have an application that has an mdc variable. How can I make a proper filter, so that if variable = test, all such output goes to one file, and to another file if variable is anything else? I tried the following (not sure how to go from there even if it worked though): <expression> mdc?.get("variable") ~= /test/ </expression> but the result is ERROR in ch.qos.logback.classic.boolex.JaninoEventEvaluator@7d55b9f - Could not start evaluator with expression [mdc?.get("variable") ~= /test/ )] Any suggestions? Thanks

2 9

Logback docs: Basic configuration example uses layout instead of encoder
by Stevo Slavić 15 Jun '12

15 Jun '12

Hello Logback community, Several times when searching for initial basic logback configuration file, I'd end up at http://logback.qos.ch/manual/joran.html and use basic configuration example, but then I'd get error/warning message by logback at runtime about deprecated configuration option with reference to http://logback.qos.ch/codes.html#layoutInsteadOfEncoder Is there any valid reason for this example to still use deprecated stuff? Kind regards, Stevo.

2 1

Release of logback version 1.0.5
by ceki 15 Jun '12

15 Jun '12

Hello all, I am happy to announce the release of logback version 1.0.5. This release adds support for ANSI coloring. It should hit the Maven central repository within the next 2 hours. Please refer to the news page for precise details of this release. 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 Enjoy, -- Ceki http://twitter.com/#!/ceki

5 11