January 2011 - logback-user

How does JMX logging level setting effect multiple appenders with different logging levels?
by JW 14 Jan '11

14 Jan '11

Hello, In my application, I have two different file appenders. One outputs general application logging (com.mypackage set to INFO), the other outputs tracing information to a separate file (com.mypackage set to TRACE). If I were to connect via jmx and set the com.mypackage to WARN, what would happen? If appenders could have different logging levels, will the JMX setting overwrite both? -Josh

1 0

Re: [logback-user] DbAppender does not write log messages to Oracle
by Sumanth Donthi 13 Jan '11

13 Jan '11

Ceki, Thanks for the reply. I get the following exception. DBAppenderBase.java(line 99) points me to EVENT_ID column in DB. I've used oracle.sql dialect found under logback-0.9.27\logback-classic\src\main\java\ch\qos\logback\classic\db\dialect directory. --------------------------------------------------------------------------------------------------------------------------------- 09:19:09,951 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - Adding ReconfigureOnChangeFilter as a turbo filter 09:19:09,951 |-INFO in ch.qos.logback.core.joran.action.StatusListenerAction - Adding status listener of type [ch.qos.logback.core.status.OnConsoleStatusListener] 09:19:09,951 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.classic.db.DBAppender] 09:19:09,966 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [DB2] 09:19:13,326 |-INFO in ch.qos.logback.core.db.DriverManagerConnectionSource@3a763a76 - Driver name=Oracle JDBC driver 09:19:13,326 |-INFO in ch.qos.logback.core.db.DriverManagerConnectionSource@3a763a76 - Driver version=11.1.0.7.0-Production 09:19:13,326 |-INFO in ch.qos.logback.core.db.DriverManagerConnectionSource@3a763a76 - supportsGetGeneratedKeys=true 09:19:13,326 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to TRACE 09:19:13,326 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [DB2] to Logger[ROOT] 09:19:13,326 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration. 09:19:15,998 |-ERROR in ch.qos.logback.classic.db.DBAppender[DB2] - problem appending event java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 14 at java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 14 at at oracle.jdbc.driver.OracleSql.computeBasicInfo(OracleSql.java:950) at at oracle.jdbc.driver.OracleSql.getSqlKind(OracleSql.java:623) at at oracle.jdbc.driver.OraclePreparedStatement.<init>(OraclePreparedStatement.java:1212) at at oracle.jdbc.driver.T4CPreparedStatement.<init>(T4CPreparedStatement.java:28) at at oracle.jdbc.driver.T4CDriverExtension.allocatePreparedStatement(T4CDriverExtension.java:68) at at oracle.jdbc.driver.PhysicalConnection.prepareStatement(PhysicalConnection.java:3140) at at oracle.jdbc.driver.PhysicalConnection.prepareStatement(PhysicalConnection.java:3042) at at oracle.jdbc.driver.PhysicalConnection.prepareStatement(PhysicalConnection.java:6022) at at ch.qos.logback.core.db.DBAppenderBase.append(DBAppenderBase.java:99) at at ch.qos.logback.core.UnsynchronizedAppenderBase.doAppend(UnsynchronizedAppenderBase.java:88) at at ch.qos.logback.core.spi.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:64) at at ch.qos.logback.classic.Logger.appendLoopOnAppenders(Logger.java:285) at at ch.qos.logback.classic.Logger.callAppenders(Logger.java:272) at at ch.qos.logback.classic.Logger.buildLoggingEventAndAppend(Logger.java:473) at at ch.qos.logback.classic.Logger.filterAndLog_0_Or3Plus(Logger.java:427) at at ch.qos.logback.classic.Logger.info(Logger.java:631) at at com.boeing.siai.lf4j.impl.AIAudit.audit(AIAudit.java:63) at at com.boeing.siai.lf4j.test.AITester.main(AITester.java:35) 09:19:18,591 |-ERROR in ch.qos.logback.classic.db.DBAppender[DB2] - problem appending event java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 14 ------------------------------------------------------------------------------------------------------------------------------------

1 0

DbAppender does not write log messages to Oracle DB
by Sumanth Donthi 13 Jan '11

13 Jan '11

Do not see records logging into Oracle 11.1 tables using logback. The three tables( logging_event, logging_event_exception, logging_event_exception) exist in Oracle DB. Note: I've tried replacing ojdbc6.jar and ojdbc5.jar logback still the result is same. No records in DB ---------------------------------DBlogback.xml----------------------------------- <configuration debug="true" scan="true" scanPeriod="3 seconds"> <property name="hostName" value="localhost"/> <property name="port" value="1521"/> <property name="sid" value="test"/> <property name="user" value="admin"/> <property name="password" value="admin"/> <appender name="DB2" class="ch.qos.logback.classic.db.DBAppender"> <connectionSource class="ch.qos.logback.core.db.DriverManagerConnectionSource"> <driverClass>oracle.jdbc.driver.OracleDriver</driverClass> <url>jdbc:oracle:thin:@${hostName}:${port}:${sid}</url> <user>${user}</user> <password>${password}</password> </connectionSource> </appender>  <root level="TRACE"> <appender-ref ref="DB2" /> </root> </configuration> --------------------------------------------------------------------------------------- The following log output shows no errors tried both DB2 and DB3 appenders the result is same. Log records won't get inserted into none of the tables. 22:15:44,015 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback.groovy] 22:15:44,015 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml] 22:15:44,015 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback.xml] 22:15:44,015 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Setting up default configuration. 22:15:44,218 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - Setting ReconfigureOnChangeFilter scanning period to 3 seconds 22:15:44,218 |-INFO in ch.qos.logback.classic.turbo.ReconfigureOnChangeFilter@2ab32ab3 - Will scan for changes in file [C:\workspace\LogTest\com\test\DBlogback.xml] every 3 seconds. 22:15:44,218 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - Adding ReconfigureOnChangeFilter as a turbo filter 22:15:44,234 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.classic.db.DBAppender] 22:15:44,234 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [DB2] 22:15:47,593 |-INFO in ch.qos.logback.core.db.DriverManagerConnectionSource@6b746b74 - Driver name=Oracle JDBC driver 22:15:47,593 |-INFO in ch.qos.logback.core.db.DriverManagerConnectionSource@6b746b74 - Driver version=11.1.0.7.0-Production 22:15:47,593 |-INFO in ch.qos.logback.core.db.DriverManagerConnectionSource@6b746b74 - supportsGetGeneratedKeys=true 22:15:47,609 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to TRACE 22:15:47,609 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [DB2] to Logger[ROOT] 22:15:47,609 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration. ---------------------------------------------------------------------------------------- ----------------------------------------------------------------------------- The following jars are in the classpath of the sample project slf4j-api-1.6.1.jar logback-core-0.9.27.jar logback-classic-0.9.27.jar logback-access-0.9.27.jar commons-compiler.jar commons-compiler-jdk.jar janino.jar ojdbc6.jar Oracle version 11.1 ----------------------------------------------------------------------------------------- package com.test import java.net.URL; import org.slf4j.Logger; import org.slf4j.LoggerFactory; import ch.qos.logback.classic.joran.JoranConfigurator; import ch.qos.logback.classic.LoggerContext; import ch.qos.logback.core.joran.spi.JoranException; import ch.qos.logback.core.util.Loader; import ch.qos.logback.core.util.StatusPrinter; public class LogTest { public static void main(String[] args) { Logger logger = LoggerFactory.getLogger("LogTest"); try { configureViaXML_File(); logger.info("Testing Status Text {}, {}","123", "test"); logger.debug("Test Parameterized {} {} {} {} {}",new Object[] {1, 2,3,4,5}); } catch(Exception ex) { logger.error("Exception in this LogTest message.",ex); ex.printStackTrace(); } } static void configureViaXML_File() { LoggerContext lc = (LoggerContext) LoggerFactory.getILoggerFactory(); try { JoranConfigurator configurator = new JoranConfigurator(); configurator.setContext(lc); lc.stop(); URL url = Loader.getResourceBySelfClassLoader("com/test/DBlogback.xml"); configurator.doConfigure(url); } catch (JoranException je) { StatusPrinter.print(lc); } } } ----------------------------------------------------------------------------------------------

2 1

FileNamePattern [] does not contain a valid DateToken
by Jonas Pacheco 12 Jan '11

12 Jan '11

I'm having a 'FileNamePattern [] does not contain a valid DateToken' exception on run time. This happens only on Windows 7 x64 running on a JVM x86 or x64. My configuration file: <?xml version="1.0" encoding="UTF-8"?> <configuration> <appender name="APP" class="ch.qos.logback.core.rolling.RollingFileAppender"> <File>${APP_HOME}\logs\app\app.log</File> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern>${APP_HOME}\logs\app\app.%d.gz</FileNamePattern> <MaxHistory>30</MaxHistory> </rollingPolicy> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern>%-5level %date{dd/MM/yy HH:mm:ss} [%thread] %logger{20} - %X{state} - %X{identity}%n%msg%n%n</Pattern> </layout> </appender> <logger name="net.app" additivity="false" level="debug"> <appender-ref ref="APP"/> </logger> <root level="info"> <appender-ref ref="APP"/> </root> </configuration> Stdout information: 09:54:48,807 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender] 09:54:48,807 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [APP] 09:54:48,901 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Pushing component [rollingPolicy] on top of the object stack. 09:54:48,901 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Adding parent to RollingPolicy: APP 09:54:48,948 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Will use gz compression 09:54:48,948 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@11:22 - RuntimeException in Action for tag [rollingPolicy] java.lang.IllegalStateException: FileNamePattern [C:\Program Files (x86)\app\logs\app\app.%d.gz] does not contain a valid DateToken at java.lang.IllegalStateException: FileNamePattern [C:\Program Files (x86)\app\logs\app\app.%d.gz] does not contain a valid DateToken at at ch.qos.logback.core.rolling.TimeBasedRollingPolicy.start(TimeBasedRollingPolicy.java:87) at at ch.qos.logback.core.joran.action.NestedComplexPropertyIA.end(NestedComplexPropertyIA.java:159) at at ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:307) at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:187) at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:174) at at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:48) at at ch.qos.logback.core.joran.spi.Interpreter.play(Interpreter.java:324) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:109) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:76) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:40) at at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:47) at at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:108) at at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:85) at at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:56) at at org.slf4j.LoggerFactory.getSingleton(LoggerFactory.java:189) at at org.slf4j.LoggerFactory.bind(LoggerFactory.java:112) at at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:105) at at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:235) at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:208) at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:221) at at br.com.ibnetwork.xingu.container.impl.ContainerSupport.<init>(ContainerSupport.java:23) at at br.com.ibnetwork.xingu.container.impl.Pulga.<init>(Pulga.java:39) at at br.com.ibnetwork.xingu.container.ContainerUtils.createContainer(ContainerUtils.java:70) at at br.com.ibnetwork.xingu.container.ContainerUtils.getContainer(ContainerUtils.java:62) at at app.daemon.DaemonRunner.configure(DaemonRunner.java:42) at at app.daemon.DaemonRunner.main(DaemonRunner.java:61) at at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at at java.lang.reflect.Method.invoke(Unknown Source) at at app.Launcher.launch(Launcher.java:42) at at app.Launcher.main(Launcher.java:26) 09:54:48,948 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@13:59 - no applicable action for [layout], current pattern is[[configuration][appender][layout]] 09:54:48,948 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@14:18 - no applicable action for [Pattern], current pattern is [[configuration][appender][layout][Pattern]]

3 9

nested markers without displaying contained children?
by Lars Fischer 12 Jan '11

12 Jan '11

Hello, I have nested markers and do they display using a PatternLayout. [%-18.18marker] results in something like this: ... [Parent [ Child ]] ... Is is possible to prevent the displaying of the contained children markers? I could not find such a feature in the documentation. If this is not possible now, can I file a feature request for this? Best regards, Lars

1 0

commons-compiler required?
by Eric Hough 11 Jan '11

11 Jan '11

Hi, I'm using Janino with logback to utilize evaluators after installing Janino as described at http://logback.qos.ch/setup.html. It's working great. However I noticed that over on Janino's site (http://docs.codehaus.org/display/JANINO/Download#Download-installation) they require commons-compiler.jar. My question is, does Logback also require commons-compiler.jar? I just want to make sure I don't run into a ClassNotFoundException down the road. Thanks!

2 2

Windows Event Log appender
by Dan Godfrey 11 Jan '11

11 Jan '11

Hi, Is there a Logback appender that will append messages to the Windows Event Log? I've been unable to find any mention of one with Google, I'm just wondering if I've missed it. Thanks, Dan.

2 1

Auto archiving log files
by Stevo Slavić 08 Jan '11

08 Jan '11

Hello Logback users, If I understood docs well, it's enough to end FileNamePattern with .zip or .gz and it will automtically get archived when rottated (TimeBasedRollingPolicy). Is that true? If yes, than something else must be preventing it to work as expected on my setup. All I see along with log files for each day, a file is created e.g. "webapp.log2456797635721192.tmp" with different numbers after "webap.log", and it's a text file - no zip file gets created. I'm using latest logback, 0.9.27, see appender definition [1]. Does anyone have idea what could be the problem? Regrads, Stevo. [1] appender definition <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <File>/var/log/tomcat6/webapp.log</File> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern>webapp.%d{yyyy-MM-dd}.log.zip</FileNamePattern> </rollingPolicy> <encoder class="ch.qos.logback.classic.encoder.PatternLayoutEncoder"> <Pattern>[%d{yyyy-MM-dd HH:mm:ss.SSS}] [%thread] %-5level %logger{35} - %msg%n</Pattern> </encoder> </appender>

1 1

logger option with string format, argument array and throwable
by Merritt H Derr 07 Jan '11

07 Jan '11

This is for Logback 0.9.27. When logging using DBAppender, The argument fields in the database table logging_event are filled using the arguments from the log statement when used in for example the debug(String format, Object[] arguments) format. For the case where I want to log with a throwable included that would land in the logging_event_exception table, there is no debug method that will take a format, argument array and throwable, so I can't log using a format and argument array and hence, all the argument fields (Arg0, Arg1, Arg2, Arg3) are left blank in the logging_event table. Other than storing those arguments in the MDC for this case, is there another work around? Or am I just missing something simple? Thanks, Merritt Derr Join us on Facebook at www.facebook.com/NYCMInsurance. ***CONFIDENTIALITY NOTICE*** This email and any attachments to it are confidential and intended solely for the individual or entity to whom it is addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you have received this email in error, please contact the sender by reply email and destroy all copies of the original message.

2 2

Specifying SYSLOGTAG portion of syslog message using SyslogAppende
by Sujith Sukumaran 06 Jan '11

06 Jan '11

How can users specify the tag portion of a syslog message using the SyslogAppender. Is there a tag property on the SyslogAppender ?. So, if message is logged it would automatically prefix the message with the tag. Regards, Sujith

2 1