- logback-user - mailman3.qos.ch

Re: [logback-user] technical question
by Ayman Hammoudeh 15 Sep '09

15 Sep '09

Hello, I have a problem with TimeBasedRollingPolicy and that is older files are not deleted when I set the MaxHistory property for example to '2' but files roll over normally every day , so any suggestions. So my question is why files older that 2 days from the current date are not deleted. Here is my XML file: <configuration> <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern>RollTimeTest.%d.log</FileNamePattern>  <MaxHistory>2</MaxHistory> </rollingPolicy> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern>%d{HH:mm:ss.SSS}[%thread] %-5level %logger{35} - %msg%n</Pattern> </layout> </appender> <root level="debug"> <appender-ref ref="FILE" /> </root> </configuration> Regards, Ayman Hammoudeh

1 0

technical question
by Ayman Hammoudeh 15 Sep '09

15 Sep '09

Hello, I have a problem with TimeBasedRollingPolicy and that is older files are not deleted when I set the MaxHistory property in the xml,so any suggestions. Here is my XML file: <configuration> <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern>RollTimeTest.%d.log</FileNamePattern>  <MaxHistory>2</MaxHistory> </rollingPolicy> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern>%d{HH:mm:ss.SSS}[%thread] %-5level %logger{35} - %msg%n</Pattern> </layout> </appender> <root level="debug"> <appender-ref ref="FILE" /> </root> </configuration> Regards, Ayman Hammoudeh

2 1

Re: [logback-user] Custom formatting of parameterized string
by david_z 14 Sep '09

14 Sep '09

RossJ wrote: > > Hello, > > I would like to be able to use parameterized logging with a byte[] > argument (formatted as a hex string). Obviously this doesn't work today > because arrays don't have a toString() implementation. > > One way I can see to do this is to modify (or substitute) the > ch.qos.logback.classic.pattern.MessageConverter class and base my > implementation on the org.slf4j.helpers.MessageFormatter class. I can > either build my own logback.jar or manipulate the classpath to make it > active. > > Is there a better way to do this? Is customization of the parameterized > formatting an area that is likely to be enhanced in future releases? Or is > my requirement somehow unusual... > > /Thanks, Ross. > > Hi, I'm new to logback and am in the process of evaluating as a replacement for log4j. A question was raised today at work regarding parameterized logging and the ability to modify logback to support java.text.MessageFormat style formatting in order to, for example, perform date or currency formatting: log.debug("myDate={0,date,MMM d}", myDate); log.debug("myAmount={0,number,currency}", myAmount); or to defer array formatting, similar to the question I'm replying to above. I appreciate the performance reasons for logback using {} replacement, but it seems like it should be possible to allow the user to provide an alternate formatting strategy if they so desire without negatively impacting the default's performance. Creating my own MessageConverter, as suggested above, to perform this formatting works fine, except the conversion is performed once per appender per event rather than just once per event. Is there a better way to handle this custom formatting goal? If not, I have a suggestion for an enhancement. 1. Add a Formatter interface with the method String format(String messagePattern, Object[] argArray) 2. The LoggingEvent would need access to the formatter. Ideally the Formatter could be configured via the config file as the Converters can be. I don't know enough about the source to flesh this part out well. 3. Modify getFormattedMessage() in the ILoggingEvent implementations public String getFormattedMessage() { if (formattedMessage != null) { return formattedMessage; } if (argumentArray != null) { if (formatter == null) { formattedMessage = MessageFormatter.arrayFormat(message, argumentArray); } else { formattedMessage = formatter.format(message, argumentArray); } } else { formattedMessage = message; } return formattedMessage; } What do you think? Thanks, David -- View this message in context: http://www.nabble.com/Custom-formatting-of-parameterized-string-tp13972167p… Sent from the Logback User mailing list archive at Nabble.com.

4 4

Turn off the verbose message from logback
by prpaudel 14 Sep '09

14 Sep '09

Hello: I am programatically configuring Logback however providing two properties that our client can set to change the Log Level and root folder to generate logs at runtime. But, my problem is that Logback framework is giving me a some verbose message that I have copied below for every execution of the problem that I should not be displaying on the console. Is there any way to turn off this message? I tried debug="true" for <configuration .../> tag but did not work. Any help will be highly appreciated. The verbose message I gets:- 9:44:22,872 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml] 09:44:22,872 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback.xml] at [/bin/logback.xml] 09:44:22,935 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not set 09:44:22,935 |-ERROR in ch.qos.logback.core.joran.action.PropertyAction - In <property> element, either the "file" attribute alone, or the "resource" element alone, or both the "name" and "value" attributes must be set. 09:44:22,935 |-ERROR in ch.qos.logback.core.joran.action.PropertyAction - In <property> element, either the "file" attribute alone, or the "resource" element alone, or both the "name" and "value" attributes must be set. Thanks. -- View this message in context: http://www.nabble.com/Turn-off-the-verbose-message-from-logback-tp25361264p… Sent from the Logback User mailing list archive at Nabble.com.

2 5

Lots of newbie questions :P
by Nitro Star 13 Sep '09

13 Sep '09

Hi! I have been playing with logback for a couple of days and find a lot of its functionality amazing! I have a couple of questions that I was wondering if I could address! I'm using logback to log information about a java server that I'm setting up. I want my log files to change every half hour and to never exceed 500MB. I would also like the logging system to cache 16MB of data before flushing to disk! Finally, I want the fileNamePattern to depend on the hostname where I'm running the server! So this are my questions: a. I have found a way for the log files to change every hour, but not every half hour... Is there a way to do this? Is there a way I can define my own RollingPolicy? b. Is there a way for me to define the fileNamePattern somewhere else other than in the logback.xml file? c. Is there a flush() function I can call when my server exists? For b. I have tried something like: LoggerContext lc = (LoggerContext) LoggerFactory.getILoggerFactory(); Logger logger = lc.getLogger("ROOT"); RollingFileAppender<ILoggingEvent> app = (RollingFileAppender<ILoggingEvent>)logger.getAppender("RootFileAppender"); RollingPolicyBase rollingPolicy = (RollingPolicyBase)app.getRollingPolicy(); rollingPolicy.stop(); rollingPolicy.setFileNamePattern("bidderserver-%d{yyyy-MM-dd-HH:mm:ss}-"+hostname+"-ip.%i.log"); rollingPolicy.start(); But that doesn't seem to work :( I'm attaching my current logback.xml file. Any and all help would be much appreciated! Also, I tried visiting #qos.ch in freenode, but there's noone there except me! Thanks again, Daniel

2 2

Re: [logback-user] RollingFileAppender specified in included resource (scouredimage)
by José Juan Montiel 13 Sep '09

13 Sep '09

Hi, >> I can't seem to get a RollingFileAppender specified in an included >> resource to function (Does not roll over!). Whereas, another >> RollingFileAppender in the main logback.xml files works just fine! Any >> ideas on what I'm doing wrong here? One questions. Where is placed profiler.xml? Near logback.xml? Or in other "relative" path? I said, because, rollingPolicy not make a dir, if it dosen't exist. Maybe, the relative path of profiler.xml ../log/ doesn't exists. Hope that helps. >> Thanks in advance! >> >> =logback.xml= >> <configuration debug="true"> >> >> <include resource="profiler.xml"/> >> >> <appender name="ConsoleAppender" >> class="ch.qos.logback.core.ConsoleAppender"> >> <Target>System.out</Target> >> <layout class="ch.qos.logback.classic.PatternLayout"> >> <Pattern>%date [%thread] %-5level %logger{26} - >> %msg%n%ex{full}</Pattern> >> </layout> >> </appender> >> >> <appender name="fileAppender" >> class="ch.qos.logback.core.rolling.RollingFileAppender"> >> <File>../logs/fetch.log</File> >> <Append>true</Append> >> <Encoding>UTF-8</Encoding> >> <rollingPolicy >> class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> >> <FileNamePattern>../logs/fetch.%d.log.gz</FileNamePattern> >> <MaxHistory>30</MaxHistory> >> </rollingPolicy> >> <layout class="ch.qos.logback.classic.PatternLayout"> >> <Pattern>%date [%thread] %-5level \(%class{26}:%line\) - >> %msg%n%ex{full}</Pattern> >> </layout> >> </appender> >> >> <logger name="com.acme" level="trace"/> >> >> <root level="info"> >> <appender-ref ref="ConsoleAppender"/> >> <appender-ref ref="fileAppender"/> >> </root> >> >> </configuration> >> >> =profiler.xml= >> <included> >> >> <appender name="ProfileAppender" >> class="ch.qos.logback.core.rolling.RollingFileAppender"> >> <File>../logs/profile.log</File> >> <Append>true</Append> >> <Encoding>UTF-8</Encoding> >> <rollingPolicy >> class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> >> <FileNamePattern>.../logs/profile.%d.log.gz</FileNamePattern> >> <MaxHistory>60</MaxHistory> >> </rollingPolicy> >> <layout class="ch.qos.logback.classic.PatternLayout"> >> <Pattern>%msg%n</Pattern> >> </layout> >> </appender> >> >> <logger name="com.acme.util.profiler" level="info"> >> <appender-ref ref="ProfileAppender"/> >> </logger> >> >> </included> >> [file:/foo/bar/WEB-INF/classes/logback.xml] >> 19:45:47,106 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Will >> use the pattern .../logs/profile.%d.log for the active file >> 19:45:47,112 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - The >> date pattern is 'yyyy-MM-dd' from file name pattern >> '.../logs/profile.%d.log.gz'. >> 19:45:47,226 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Will >> use the pattern ../logs/server.%d.log for the active file >> 19:45:47,227 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - The >> date pattern is 'yyyy-MM-dd' from file name pattern >> '../logs/server.%d.log.gz'. -- Jose Juan Montiel Martinez Eurobits Technologies Calle Musgo 3, 1ª Planta 28023 Madrid T +34-917080300 F +34-913077480 josejuan.montiel(a)eurobits.es http://www.eurobits.com

3 2

RollingFileAppender specified in included resource
by scouredimage 08 Sep '09

08 Sep '09

Hi, I can't seem to get a RollingFileAppender specified in an included resource to function (Does not roll over!). Whereas, another RollingFileAppender in the main logback.xml files works just fine! Any ideas on what I'm doing wrong here? Thanks in advance! =logback.xml= <configuration debug="true"> <include resource="profiler.xml"/> <appender name="ConsoleAppender" class="ch.qos.logback.core.ConsoleAppender"> <Target>System.out</Target> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern>%date [%thread] %-5level %logger{26} - %msg%n%ex{full}</Pattern> </layout> </appender> <appender name="fileAppender" class="ch.qos.logback.core.rolling.RollingFileAppender"> <File>../logs/fetch.log</File> <Append>true</Append> <Encoding>UTF-8</Encoding> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern>../logs/fetch.%d.log.gz</FileNamePattern> <MaxHistory>30</MaxHistory> </rollingPolicy> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern>%date [%thread] %-5level \(%class{26}:%line\) - %msg%n%ex{full}</Pattern> </layout> </appender> <logger name="com.acme" level="trace"/> <root level="info"> <appender-ref ref="ConsoleAppender"/> <appender-ref ref="fileAppender"/> </root> </configuration> =profiler.xml= <included> <appender name="ProfileAppender" class="ch.qos.logback.core.rolling.RollingFileAppender"> <File>../logs/profile.log</File> <Append>true</Append> <Encoding>UTF-8</Encoding> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern>.../logs/profile.%d.log.gz</FileNamePattern> <MaxHistory>60</MaxHistory> </rollingPolicy> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern>%msg%n</Pattern> </layout> </appender> <logger name="com.acme.util.profiler" level="info"> <appender-ref ref="ProfileAppender"/> </logger> </included> =debug log= 19:45:46,708 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml] 19:45:46,709 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback.xml] at [file:/foo/bar/WEB-INF/classes/logback.xml] 19:45:46,893 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender] 19:45:46,910 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [ProfileAppender] 19:45:46,974 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Pushing component [rollingPolicy] on top of the object stack. 19:45:46,982 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Adding parent to RollingPolicy: ProfileAppender 19:45:47,103 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Will use gz compression 19:45:47,106 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Will use the pattern .../logs/profile.%d.log for the active file 19:45:47,112 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - The date pattern is 'yyyy-MM-dd' from file name pattern '.../logs/profile.%d.log.gz'. 19:45:47,112 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Roll-over at midnight. 19:45:47,173 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Pushing component [layout] on top of the object stack. 19:45:47,196 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[ProfileAppender] - Active log file name: ../logs/profile.log 19:45:47,196 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[ProfileAppender] - File property is set to [../logs/profile.log] 19:45:47,208 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Popping appender named [ProfileAppender] from the object stack 19:45:47,209 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.acme.util.profiler] to INFO 19:45:47,209 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting additivity of logger [com.acme.util.profiler] to true 19:45:47,209 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [ProfileAppender] to Logger[com.acme.util.profiler] 19:45:47,212 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender] 19:45:47,214 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [ConsoleAppender] 19:45:47,217 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Pushing component [layout] on top of the object stack. 19:45:47,225 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Popping appender named [ConsoleAppender] from the object stack 19:45:47,225 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender] 19:45:47,225 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [fileAppender] 19:45:47,226 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Pushing component [rollingPolicy] on top of the object stack. 19:45:47,226 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Adding parent to RollingPolicy: fileAppender 19:45:47,226 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Will use gz compression 19:45:47,226 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Will use the pattern ../logs/server.%d.log for the active file 19:45:47,227 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - The date pattern is 'yyyy-MM-dd' from file name pattern '../logs/server.%d.log.gz'. 19:45:47,227 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Roll-over at midnight. 19:45:47,227 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Pushing component [layout] on top of the object stack. 19:45:47,228 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[fileAppender] - Active log file name: ../logs/server.log 19:45:47,228 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[fileAppender] - File property is set to [../logs/server.log] 19:45:47,228 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Popping appender named [fileAppender] from the object stack 19:45:47,228 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.acme] to TRACE 19:45:47,228 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting additivity of logger [com.acme] to true 19:45:47,228 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to INFO 19:45:47,228 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [ConsoleAppender] to Logger[root] 19:45:47,228 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [fileAppender] to Logger[root] 19:45:47,228 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration. -- View this message in context: http://www.nabble.com/RollingFileAppender-specified-in-included-resource-tp… Sent from the Logback User mailing list archive at Nabble.com.

1 1

Lost internet connectivity
by Ceki Gulcu 05 Sep '09

05 Sep '09

Hello all, There was a wiring problem in our building (qos.ch) where cal10n, logback and slf4j projects are hosted. As consequence, our various web-sites were unreachable for about 12 hours. The issue was fixed just a few minutes ago with the help of our internet provider. We are currently working on duplicating parts of our infrastructure so that such connectivity problems if they re-occur, will have much less of an impact. My apologies for the inconvenience. -- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch

1 0

same layout - different results
by Rob Lister 04 Sep '09

04 Sep '09

Hi Folks, Sending events to a zOS syslog via a fileappender;  <appender name="FILEAPPENDER" class="org.apache.log4j.FileAppender"> <param name="Append" value="true"/> <param name="File" value="/dev/console"/> <layout class="com.es.event.layout.JSFEventTextLay <param name="LayoutClass" value="org.apache.log4j.PatternLayout"/> <param name="LayoutParam1" value= </layout>  <param name="Threshold" value="INFO"/> <filter class="com.es.event.filter.SystemEventFilter"/> <filter class="org.apache.log4j.varia.DenyAllFilter"/> </appender> On our system in US, I get; INFO - ACIJMX 6010 5 Output logged to console of Process RFSH: On clients site in Europe; INFO - ÝACIJMX¨ Ý6010¨ Ý5¨ Output logged to console of Process RFSH: Anyone hit this before on Z, or more specifically zOS /Unix System Services? Regards, Rob Lister"%-5p %x - %m%n"/>

2 1

Re: [logback-user] Verbose status messages, even though no errors or warnings
by Rob W 28 Aug '09

28 Aug '09

Aha, so that's what it was. I can't believe I completely missed that. Serves me right for copying and pasting the example configuration and not checking *all* the settings in it. Thank you very much Ceki! Ceki Gulcu wrote: > Does the /analytics/dist/conf/logback.xml file contain the > "debug" attribute set to true in the <configuration> element?

2 1