June 2014 - logback-user - mailman3.qos.ch

Log rotation every 12 hrs at noon and mid night
by srinandina＠gmail.com 11 Jun '14

11 Jun '14

I have defined TimeBasedRollingPolicy using: <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">  <fileNamePattern>${log.dir}/app.log.%d{yyyy-MM-dd-a}</fileNamePattern> </rollingPolicy> But the log file is being rotated only once a day at 12 AM. Looking at the code PeriodicityType enum has an entry 'HALF_DAY' but is not present in the valid list. Is this supported by logback? Thanks, Srinivas

1 0

Recognize OSGi bundle resource in ConfigurationWatchList.convertToFile
by Ashwin Jha 10 Jun '14

10 Jun '14

Hi, The current implementation of ConfigurationWatchList.convertToFile returns null when the URL type is not file. Due to this automatic reloading on change of configuration does not work in OSGi bundles. This problem occurs even if you use a fragment. As in any case, the logback.xml file will be recognized as bundleresource type and not as file type. This is necessary as the logback.xml config file is recognized during the start up time. So, it creates confusion as the file is found first time around and then the reloading does not occur. And, this is not mentioned in the documentation either. Given that logback has a p2 repository for OSGi support, IMHO this feature is a must. BTW I would love to contribute this feature. Regards, Ashwin

2 1

[logback-dev] Change implementation of MessageFormatter for byte[]
by Thorsten Schöning 09 Jun '14

09 Jun '14

Hi all, I have a use case where I need to log some byte[] and the current default behavior of slf4j seems to be to print decimal values for each item in the array. I would prefer hex notation instead and can't seem to find any way to configure that behavior. It seems to me it's hard coded using LoggingEvent.getFormattedMessage and MessageFormatte.byteArrayAppend. Is there any way to change this behavior? The only thing coming into my mind is overriding LoggingEvent with a custom getFormattedMessage method, but I don't know how to get Logback using that internally. And I wouldn't want to re-implement MessageFormatter because it's most interesting methods are private. Any other options like parsing the formatted message afterwards and convert it to contain hex bytes instead? Though it sounds a lot more difficult than converting into the format I want in the first place. Thanks for your help! Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail:Thorsten.Schoening@AM-SoFT.de AM-SoFT IT-Systeme http://www.AM-SoFT.de/ Telefon...........05151- 9468- 55 Fax...............05151- 9468- 88 Mobil..............0178-8 9468- 04 AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow _______________________________________________ logback-dev mailing list logback-dev(a)qos.ch http://mailman.qos.ch/mailman/listinfo/logback-dev

1 0

Logback Spring Extension
by Ben M 03 Jun '14

03 Jun '14

I follow the configuration described at: https://github.com/qos-ch/logback-extensions/wiki/Spring but the one piece i don't understand is: <bean class="ch.qos.logback.classic.encoder.PatternLayoutEncoder" init-method="start" destroy-method="stop"> <property name="context" value="#{ T(org.slf4j.LoggerFactory).getILoggerFactory() }"/> <property name="pattern" value="%date %-5level [%thread] %logger{36} %m%n"/> </bean> The result of org.slf4j.LoggerFactory.getILoggerFactory() is a an ILoggerFactory which shares no class hierarchy with a ch.qos.logback.core.Context. What is happening here?

1 0