- logback-user - mailman3.qos.ch

urgent explination issue
by Ayman Hammoudeh 01 Oct '09

01 Oct '09

Hello, I want to know how can I use max history in Size and time based archiving<http://logback.qos.ch/manual/appenders.html#SizeAndTimeBasedFNATP> and where exactly to put the<MaxHistory> tag in the xml , I have tried to put it in the <RollingPolisy> tag but its not working. Any help would be appreciated. Best Regards, Ayman Hammoudeh

3 6

Log only one java package
by alex 01 Oct '09

01 Oct '09

Hi, how is possible to log ONLY the log message for one specified java package ? For example I have to log only the log call from com.test.mypack.* classes. Do I have to write a filter ? Thanks a lot for all help

2 2

reference to an evaluator
by Hontvári József 29 Sep '09

29 Sep '09

Is there a way to refer to a previously defined evaluator in EvaluatorFilter instead of specifying it inline? I would like to use the same evaluator in two filters in two appenders. As I remember this is possible, but now I cannot find where it is mentioned in the manual.

2 1

ThrowableProxy and instanceof in EventEvaluator
by Hontvári József 28 Sep '09

28 Sep '09

In an event evaluator called in an option of an "ex" formatting specifier I would use a "throwable instanceof example" expression. This is the same as in Example 5.3 in the documentation, which also uses instanceof. This doesn't work because the throwable object is not a Throwable but a ThrowableProxy. Again, at another place, in the table at the beginning of the "Evaluator Filters taking Java Expressions" section in chapter Filters it is shown that the type of throwable is Throwable (annd not ThrowableProxy). Somehow I still get a ThrowableProxy instead of Throwable.

2 3

JMXConfigurator and Resource adapter (RAR)
by ad-rocha 26 Sep '09

26 Sep '09

Hi, I'm using logback in my Resource Adapter and would like to know the best practice for unregistering it. Thanks in advance, Andre -- View this message in context: http://www.nabble.com/JMXConfigurator-and-Resource-adapter-%28RAR%29-tp2557… Sent from the Logback User mailing list archive at Nabble.com.

1 0

Split long data on multiple rows
by Anders Hammar 22 Sep '09

22 Sep '09

Hi, I have a framework that utilizes logback-core for logging. Due to limitations in the software reading the log files, a new requirement is that long data should be split on multiple rows. I'm trying to figure out if there a simple way of doing this? More info: What I have is an extension of the PatternLayoutBase which adds the converters for my event class. I'm using the standard RollingFileAppender. So, let's say I have a FooConverter, which gets the foo info from the event. But, when logging to the file, the foo info part must never be longer than x chars. If it is, it should be split on multiple rows. Other data (generated by other converters) should then be repeated. Any suggestions on how to do this in a clean logback way is appreciated! What I'm currently thinking is to loop on the converters (calling PatternLayoutBase.writeLoopOnConverters multiple times), but I need to know when that's required... Anyone done something similar? /Anders

2 4

Dual licensing logback
by Ceki Gulcu 18 Sep '09

18 Sep '09

Hello all, After a very long investigation resulting in a better understanding of licensing issues, I think dual-licensing logback under EPL 1.0 and LGPL 2.1 would help with the project's adoption. Licensees can then choose either the terms of the EPL or the terms of the LGPL when they use logback. The EPL license will placate organizations which refuse the restrictions imposed by the LGPL whereas the LGPL license ensures continuity in licensing and also keeps the door open for licensees already bound by the terms of (L)GPL. Comments? ps. If you intend to respond, please do so on logback-users@. -- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch

4 3

Urgent Technical Issue
by Ayman Hammoudeh 16 Sep '09

16 Sep '09

Hello, I have a problem with TimeBasedRollingPolicy and that is older files are not deleted when I set the MaxHistory property let's say for example '2' it should delete files that are older than two days right??? But it doesn't delete any files!!!??? 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> Any help would be appreciated. Regards, Ayman Hammoudeh

2 1

Time Based Rollover in 0.9.17
by Stephen Duncan Jr 16 Sep '09

16 Sep '09

I've noticed that some of my applications using logback have stopped doing their time-based rollover. This change coincides with my upgrade of those apps from 0.9.16 to 0.9.17. These are apps that do not run continously - they are kicked off via cron a couple times a day. Those processes that do run continuously (such as the webserver) do still rollover correctly. Anyone else seen this change in behaviour? Is there any change in configuration needed for 0.9.17? Or is it a bug? -- Stephen Duncan Jr www.stephenduncanjr.com

2 5

Always log, regardless of level, but not as ERROR
by laboo 15 Sep '09

15 Sep '09

I'm looking for a way to always log a message regardless of the current level of logger. My application allows the user to change the level via JMX and I always want to log a message that says, "The level was changed from X to Y". I *could* accomplish this by specifying the highest level, ERROR, but it's not an error, and I don't want it to show up as one. In log4j, I was able to accomplish this by using the log() method with level OFF (strangely enough). I tried doing something similar with logback's level ALL, but it's not accepted as valid level to the log() method. Is there a different/better way to accomplish this? Thanks, Laboo -- View this message in context: http://www.nabble.com/Always-log%2C-regardless-of-level%2C-but-not-as-ERROR… Sent from the Logback User mailing list archive at Nabble.com.

3 3