November 2014 - logback-user

MS SQL Server script error
by Dário Abdulrehman 27 Nov '14

27 Nov '14

Hi, The change that is documented in the mssql.sql script https://github.com/qos-ch/logback/blob/edc0fe2340782a592f9fd8329287d8ea5557… as "The event_id column type was recently changed from INT to DECIMAL(40) without testing." does not work in MS SQL Server 2008 R2. It issues the following error: Column or parameter #15: Specified column precision 40 is greater than the maximum precision of 38. Changing the mentioned fields to DECIMAL(38) fixes the problem but perhaps it is better to revert back to INT? Thanks, Dário

2 1

How do I eliminate logging from a specific jar
by rails 26 Nov '14

26 Nov '14

I am using slf4j over logback in java. How do I eliminate logging from a specific jar? It prints a lot of info and I want to raise only its level to debug.

3 2

Logback question
by Russ Lavoie 19 Nov '14

19 Nov '14

Hello, I am having issues using the Asyncappender for logback with the following configuration. <snip> <?xml version="1.0" encoding="UTF-8"?> <configuration>  <appender name="accessLog" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>/mnt/log/jetty/jetty_access.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <param name="FileNamePattern" value="/mnt/log/jetty/jetty_access.log.%d{yy-MM-dd}.gz" /> <maxHistory>7</maxHistory> <maxFileSize>1M</maxFileSize> </rollingPolicy> <layout class="ch.qos.logback.access.PatternLayout"> <param name="Pattern" value='{ "@timetamp": "%date", "clientip": "%i{x-forwarded-for}", "urlpath": "%requestURI", "status": %statusCode, "method": "%requestMethod", "referer": "%header{Referer}", "bytes": %bytesSent, "duration": %elapsedTime, "xtid": "%header{X-TID}"}' /> </layout> </appender> <appender name="asyncaccessLog" class="ch.qos.logback.classic.AsyncAppender"> <queueSize>500</queueSize> <discardingThreshold>80</discardingThreshold> <appender-ref ref="accessLog" /> </appender> <root level="trace"> <appender-ref ref="asyncaccessLog" /> </root> </configuration> </snip> It does not write the access data to file. However, if I remove the asyncaccessLog appender and the root block. Then only add the <appender-ref ref="accessLog" /> by it self after </appender> it works with no issue. It will not work if I am trying to send the accessLog appender through the asyncaccessLog appender. Can I get any help here?

1 0

Sanity Checking the Log Stream
by Eric Kolotyluk 14 Nov '14

14 Nov '14

I found an interesting problem while configuring our Amazon Kinesis Connector. After starting up our service everything looks fine, but after 15 minutes or so, all hell breaks loose. The Connector is Amazon's code, and it does not throw any exceptions that our code can catch, rather it just reports a lot of errors in the log stream. This is clearly an insane situation that we need to catch, so I was thinking of writing a custom appender, filter, or turbo-filter to monitor the log stream for insanity. For example, errors per minute over some threshold. Does this seem like the right way to address this problem? Have other people used similar techniques, or other techniques to sanity check the log stream? Cheers, Eric

2 2

Re: [logback-user] logback.xml not reloaded
by Johanes Soetanto 12 Nov '14

12 Nov '14

Upon my investigation, it seems like my problem with reloading is related to the change made in version 1.0.2 (http://jira.qos.ch/browse/LOGBACK-327 ). I tested with version 1.0.1 or 1.1.2 the configuration is not reloaded when there is change. Note: I haven't run the app on debug mode. Johanes > > Message: 4 > Date: Tue, 4 Nov 2014 10:01:11 +0000 > From: David Roussel <nabble(a)diroussel.xsmail.com> > To: logback users list <logback-user(a)qos.ch> > Subject: Re: [logback-user] logback.xml not reloaded > Message-ID: > <EEBB841D-A28F-4616-80CD-83E3A326CF70(a)diroussel.xsmail.com> > Content-Type: text/plain; charset="us-ascii" > > My only suggestion is running it in a debugging session in your IDE and > seeing what is happening that way. > > David > > > On 4 Nov 2014, at 07:34, Johanes Soetanto <otnateos(a)gmail.com> wrote: > > > > Hi there, > > > > I would like to know if there is a way to debug why logback.xml > configuration change cannot be reloaded by our application. It had been > working correctly on our application for a long time, however I discover > from a week ago that change at runtime is not applied. If i restart the > application, the change is applied properly. configuration xml is using > basic one using scan="true". > > > > I tried adding debug="true" but no information message apart from usual > logback information message before application startup. The only change I > can think of is we change Tomcat from 6.0.x to 7.0.56. We are using logback > version 1.0.13. > > > > Any assistance is appreciated. > > > > Thanks > > > > Johanes > > _______________________________________________ > > Logback-user mailing list > > Logback-user(a)qos.ch > > http://mailman.qos.ch/mailman/listinfo/logback-user >

1 0

logback.xml not reloaded
by Johanes Soetanto 04 Nov '14

04 Nov '14

Hi there, I would like to know if there is a way to debug why logback.xml configuration change cannot be reloaded by our application. It had been working correctly on our application for a long time, however I discover from a week ago that change at runtime is not applied. If i restart the application, the change is applied properly. configuration xml is using basic one using scan="true". I tried adding debug="true" but no information message apart from usual logback information message before application startup. The only change I can think of is we change Tomcat from 6.0.x to 7.0.56. We are using logback version 1.0.13. Any assistance is appreciated. Thanks Johanes

2 1

Log by transaction, rather than logger/class
by Donald McLean 03 Nov '14

03 Nov '14

I am working on a multi-threaded web app and I use Logback for debugging purposes during development. Most of what happens in my app is event driven, and there is a clear start and end point of the processing of each event. All of the processing that takes place on a given thread between the start and end point are all part of the same event/transaction. So what I would find helpful is if there was a way to configure Logback so that logging was different inside a transaction (even if it just turned on all logging) and that the rules were based on the transaction name rather than on the debugger. Would something like this be reasonably possible? Just curious, Donald

2 1