- logback-user - mailman3.qos.ch

ClassCastException with DBAppender in Logback 1.0.7
by Moebius.Jonathan＠swm.de 08 Nov '12

08 Nov '12

Hello List, I'm using the DBAppender with Logback 1.0.7 and I'm getting the following Exception: 11:54:18,066 |-ERROR in ch.qos.logback.access.db.DBAppender[DB] - problem appending event java.lang.ClassCastException: ch.qos.logback.classic.spi.LoggingEvent cannot be cast to ch.qos.logback.access.spi.IAccessEvent at java.lang.ClassCastException: ch.qos.logback.classic.spi.LoggingEvent cannot be cast to ch.qos.logback.access.spi.IAccessEvent at at ch.qos.logback.access.db.DBAppender.subAppend(DBAppender.java:36) at at ch.qos.logback.core.db.DBAppenderBase.append(DBAppenderBase.java:108) 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:280) at at ch.qos.logback.classic.Logger.callAppenders(Logger.java:267) at at ch.qos.logback.classic.Logger.buildLoggingEventAndAppend(Logger.java:449) at at ch.qos.logback.classic.Logger.filterAndLog_1(Logger.java:421) at at ch.qos.logback.classic.Logger.info(Logger.java:611) at at de.swm.pmf.logtest.LoggingThread.run(LoggingThread.java:16) at at java.lang.Thread.run(Unknown Source)" I'm not quite certain what the problem is, but I was looking through the code and have found the following: Logger.appendLoopOnAppenders has ILoggingEvent as an Parameter, this Parameter is passed through to the AppenderAttachableImpl.appendLoopOnAppenders, which is ok as the AAI is typed as AAI<ILoggingEvent>. The AAI has a List<Appender<E>> where E seems to be bound to the Type of the AAI, which is ILoggingEvent. UnsynchronizedAppenderBase is still typed as ILoggingEvent and therefore UnsynchronizedAppenderBase.doAppend takes an ILoggingEvent as Parameter and passes that through to ch.qos.logback.core.db.DBAppender.append, where we are leaving package ch.qos.logback.core.db for ch.qos.logback.access.db and the DBAppender there (a child of the core-DBAppender) is typed as DBAppender<IAccessEvent>, hence the ClassCastException. What I'm not getting is, why the code compiled originally, because clearly the DBAppender cannot be typed ILoggingEvent and IAccessEvent at the same time. I appreciate any help or pointers because searching the web gives nothing useful and I'm really stuck here. Kind regards, Jonathan My configuration is pretty much straight forward, stolen from the example: <configuration> <statusListener class="ch.qos.logback.core.status.OnConsoleStatusListener" /> <appender name="DB" class="ch.qos.logback.access.db.DBAppender"> <connectionSource class="ch.qos.logback.core.db.DriverManagerConnectionSource"> <driverClass>com.mysql.jdbc.Driver</driverClass> <url>jdbc:mysql://localhost:3306/logbackdb</url> <user>root</user> <password>mysqlroot</password> </connectionSource> <insertHeaders>false</insertHeaders> </appender> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">  <encoder> <pattern>%-4relative [%thread] %-5level - %msg%n</pattern> </encoder> </appender> <root level="debug"> <appender-ref ref="STDOUT" /> </root> <logger name="logexample" additivity="false"> <appender-ref ref="DB" /> </logger> </configuration>

2 2

Use the stack trace rendering outside of logback
by Padraic Renaghan 08 Nov '12

08 Nov '12

Really like the reverse stack trace rendering in logback and would like to leverage it (reuse it) in my app where I display the stack on an error web page. Can't seem to figure out how to get at just that function in the logback classes. Looking for something like String reverseStackRendering = LogbackExceptionUtils.renderInReverse(Throwable t) Or at least some public way to get at that function. Is that possible? Any pointers on where to start looking? Thanks, Padraic

1 0

Logback daily rollover and on every server startup
by Gaurav Kumar 07 Nov '12

07 Nov '12

Hi, With logback, is there a way to do daily Rollover AND also rollover on every server restart? I also wanted rollover based on Size, but I have seen an issue already reported about this being a bug. If not, what is the best way to do this? My setup: For daily rollover I am using the following pattern: * .... <file>${jetty.home}/logs/testapp.${dateStr}.log</file> .... ** <fileNamePattern>${jetty.home}/logs/testapp.%d{yyyy-MM-dd}.log.${timeStr}</fileNamePattern> where dateStr and timeStr are defined as: * *<timestamp key="dateStr" datePattern="yyyy-MM-dd" timeReference="contextBirth"/> <timestamp key="timeStr" datePattern="HHmmssSSS" timeReference="contextBirth"/> Also, I have the following triggering policy:* *<timeBasedFileNamingAndTriggeringPolicy class="utils. LogbackLogTriggeringPolicy"/> * *LogbackLogTriggeringPolicy.java is:* *@NoAutoStart public class LogbackLogTriggeringPolicy<E> extends DefaultTimeBasedFileNamingAndTriggeringPolicy<E> { @Override public void start() { super.start(); nextCheck = 0L; * * isTriggeringEvent(null, null); try { tbrp.rollover(); } catch (RolloverFailure e) { //Do nothing } } } With the above *LogbackLogTriggeringPolicy I am able to achieve rollover on server startup but daily rollover is not working. Any suggestions? Thanks!

1 1

Quotes doubled in logs?
by David Balažic 06 Nov '12

06 Nov '12

Hi! I the logs of our application I noticed that quotes get doubled. For example: - app received xml contents: <?xml version=''1'' ?> ... Those are two single quotes before the 1 and then two single quotes after it. That is not valid XML so the app would refuse it, but is does not. So the doubled quotes must appears somewhere in the logging. We use slf4j 1.6.1 and logback 0.9.28. Could this be something in logback? Did anyone else experience something similar? Regards, David

1 1

Custom TextAreaAppender
by m.lippa＠ads.it 06 Nov '12

06 Nov '12

Hi all, I'm switching my first java desktop application from log4j to logback, mainly because we neede a reliable DailyRollingFileAppender, and we were told the log4j implementation is not. So far all ok, we simply changed the Logger declaration and all worked well. The problem is our custom TextAreaAppender we are currently using to log the events to a text area in the application. The log4j implementation is very simple: public class TextAreaAppender extends WriterAppender { static private JTextArea jTextArea = null; public static void setTextArea(JTextArea jTextArea) { TextAreaAppender.jTextArea = jTextArea; } /** * Format and then append the loggingEvent to the stored JTextArea. */ public void append(LoggingEvent loggingEvent) { if (layout != null) { final String message = layout.format(loggingEvent); StringBuilder sb = new StringBuilder(); if (loggingEvent.getThrowableInformation() != null) { String[] stackTrace = loggingEvent.getThrowableStrRep(); for (String s : stackTrace) { sb.append(s); sb.append(Layout.LINE_SEP); } } final String stackTrace = sb.toString(); SwingUtilities.invokeLater(new Runnable() { public void run() { if (jTextArea != null) { jTextArea.append(message); if (!stackTrace.isEmpty()) { jTextArea.append(stackTrace); } } } }); } } } I worked a couple of day but did not manage to get a logback version of this appender to work. Do you have any sample code available? thanks in advance Maurizio Questa e-mail ed i suoi allegati sono ad uso esclusivo di coloro ai quali � indirizzata e potrebbe contenere informazioni riservate, la cui diffusione, copia e/o distribuzione � proibita. Qualora riceveste questo messaggio per errore, scusandoci per l'accaduto, Vi preghiamo di avvertirci immediatamente, distruggendo quanto ricevuto.

2 1

Is there a way how to retrieve, using the Logback API, the Logback path location pragmatically?
by Noomen Hamza 05 Nov '12

05 Nov '12

I have a Java/C++ application, the java part uses Backlog and I need to put the C++ part log files into the same path location as Backlog. Is there a way how to retrieve, using the Logback API, the Logback path location pragmatically (the fileNamePattern value in logback.xml) ? Thanks Noomen

1 0

Re: [logback-user] Jetty: How to get multiple web applications log to a common log file
by gaurav419＠gmail.com 04 Nov '12

04 Nov '12

3 3

Jetty: How to get multiple web applications log to a common log file
by Gaurav Kumar 01 Nov '12

01 Nov '12

Hi, I am using Jetty webserver and logback for logging. I have a scenario with multiple Web Applications (so multiple wars into jetty/webapps dir). Each war has its own copy of logback-classic, logback-core and slf4j-api. There is a common copy of logback.xml in jetty/resources (pasted below). My intent is to maintain a logfile named "testapp.<date>.log" which should be used by all the wars for logging. Further, I want a rollover of this file on every startup. I am able to achieve this except that each war is trying to create its own version of the log file so when each war is loaded it creates its own logfile archiving the earlier logfile created by the earlier war. This continues till all wars are loaded thus creating these many log files per startup. The archived files are are named "testapp.<date>.log.<time in millisec>. Is there a way to ask all wars to log into the same file? *logback.xml file content:* *<configuration> <timestamp key="dateStr" datePattern="yyyy-MM-dd" timeReference="contextBirth"/>--> <timestamp key="timeStr" datePattern="HHmmssSSS" timeReference="contextBirth"/>--> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <encoder> <pattern>%date{MMM dd}, %date{yyyy hh:mm:ss a} %class %method:%line %n%level: %message%n </pattern> </encoder> </appender> <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>${jetty.home}/logs/Baywatch.${dateStr}.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">  <fileNamePattern>${jetty.home}/logs/Baywatch.%d{yyyy-MM-dd}.log.${timeStr}</fileNamePattern>  <maxHistory>30</maxHistory> <cleanHistoryOnStart>true</cleanHistoryOnStart>  <timeBasedFileNamingAndTriggeringPolicy class="com.bmc.ola.utils. LogbackLogTriggeringPolicy"/> </rollingPolicy> <encoder> <pattern>%date{MMM dd}, %date{yyyy hh:mm:ss a} %class %method:%line %n%level: %message%n </pattern> </encoder> </appender> <root level="INFO"> <appender-ref ref="FILE" /> </root> </configuration>* *LogbackLogTriggeringPolicy.java is:* *@NoAutoStart public class LogbackLogTriggeringPolicy<E> extends DefaultTimeBasedFileNamingAndTriggeringPolicy<E> { @Override public void start() { super.start(); nextCheck = 0L; addInfo("gktest123"); isTriggeringEvent(null, null); try { tbrp.rollover(); } catch (RolloverFailure e) { //Do nothing } } } * Thanks.

3 4

SizeAndTimeBasedArchiveRemover - Unexpected periodsElapsed value 0
by Henning Juva 01 Nov '12

01 Nov '12

Hi, We currently experience a Warning logged in our stderrout log each time our application log rolls over. I think this has started after an upgrade of logback a while back. I can't find much info about what the problem might be in the forum or by googling. Anyone have an idea what the issue might be? Message: 00:02:18,709 |-WARN in ch.qos.logback.core.rolling.helper.SizeAndTimeBasedArchiveRemover@3640c655- Unexpected periodsElapsed value 0 Our appender config: <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>${basedir:-.}/../logs/foo-${artifact}.%d{yyyy-MM-dd}.%i.log.zip</fileNamePattern> <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP"> <maxFileSize>100MB</maxFileSize> </timeBasedFileNamingAndTriggeringPolicy> <maxHistory>60</maxHistory> </rollingPolicy> <encoder> <pattern>%d{HH:mm:ss.SSS} [%property{hostname}] [%thread] [%X{auth_kontoid} %X{logid}] %-5level %logger{36} - %msg%n</pattern> </encoder> </appender> Thanks, Henning

1 0

alternate configuration files on the classpath
by Steve Cohen 31 Oct '12

31 Oct '12

In the logback manual, http://logback.qos.ch/manual/configuration.html#configFileProperty, there is the following section > Specifying the location of the default configuration file as a system property > > If you wish, you can specify the location of the default configuration file with a system property named logback.configurationFile. The value of this property can be a URL, a resource on the class path or a path to a file external to the application. > > java -Dlogback.configurationFile=/path/to/config.xml chapters.configuration.MyApp1 There is no example of using this property to refer to a configuration file on the classpath, for example, an alternate configuration file deployed in an application jar file. This is my requirement. I have two executables, the main one, and an auto-installer for it, code for which lives in the same jar file, with each executable launched by its own batch file. I tried placing an alternate config file on the root of the classpath inside the jar file (at the same directory as logback.xml). this does not seem to work. What is the correct format for defining -Dlogback.configurationFile= for a resource located in a jar file on the classpath or, for that matter, any other classpath resource more generically?

3 5