- logback-user - mailman3.qos.ch

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

02 Dec '14

Finally I manage to get a time to debug the app. Looking into ReconfigureOnChangeFilter (version 1.0.13) , the execution is stopped by line #108 where the mask is always set to 65535 . I'm clueless on how to change the mask as it seems like it is being managed automatically by updateMaskIfNecessary (line #147) . I believe it was added for optimization, but with mask value of 65535, it will be a while for the configuration to be loaded even though i set my configuration to be scanned every 200 seconds. Any hint how to fix this? Thanks, Johanes > > Message: 1 > Date: Wed, 12 Nov 2014 12:10:38 +1100 > From: Johanes Soetanto <otnateos(a)gmail.com> > To: logback-user(a)qos.ch > Subject: Re: [logback-user] logback.xml not reloaded > Message-ID: > <CAHn_LrykvJuj=UF4=-YhoW+QdUb2y+iHKS9u=5wT5D= > dCv8uNA(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > 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 > > >

1 0

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

Why does DBAppender slow down logging although it has a non-matching filter?
by Simon.Erhardt＠befine-solutions.com 31 Oct '14

31 Oct '14

Hello there, we are using TomEE, SLF4J and Logback. Our aim is to log certain logging statements into a database (determined by a marker), in addition to the stdout. Here is our logback configuration: <?xml version="1.0" encoding="UTF-8"?> <configuration> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <encoder>...</encoder> </appender> <appender name="DB" class="ch.qos.logback.classic.db.DBAppender"> <connectionSource class="ch.qos.logback.core.db.DriverManagerConnectionSource"> <driverClass>oracle.jdbc.OracleDriver</driverClass> <url>...</url> </connectionSource> <filter class="ch.qos.logback.core.filter.EvaluatorFilter"> <evaluator class="ch.qos.logback.classic.boolex.OnMarkerEvaluator"> <marker>LOGDATABASE</marker> </evaluator> </filter> </appender> <root level="info"> <appender-ref ref="STDOUT" /> <appender-ref ref="DB" /> </root> </configuration> TomEE (which is configured to use SLF4J) takes about 3 times longer to startup if the DBAppender is active (14 seconds compared to 4 seconds). Although the filtering works and there are no log entries in the database for the tomcat startup. I already know that I could use connection pooling to speed up when it actually comes to database logging. But nevertheless the filter should do it in this case. My suspicion is that there are connections opened and closed during logging, even if the log statement is filtered out. Or are there any other ideas why this is so slow? Best regards, Simon Erhardt

1 1

Configure logback within an EAR
by Kantzer, Chris E 28 Oct '14

28 Oct '14

Hello, I am trying to convert our web applications which are packaged within EARs to use logback instead of log4j. I would like to separate the log messages for each application into their own log file. I'm having an issue with shared EJBs within each EAR not logging to the same log file as the web-apps. The shared EJBs all use static logger references. My artifacts are packaged as follows: EAR1.ear EJB_shared.jar Web_app_1.war EAR2.ear EJB_shared.jar Web_app_2.war Using the ContextJNDISelector and SiftingAppenders I am able to separate the log messages for the web apps, but the EJB log messages are not being logged. I'm thinking this is due to the EJB not have the same context (or an context?) as the web apps so they are not getting picked up by the SiftingAppender with my logback config xml? Is there a standard way to configure logback so that the shared EJBs are included? Do I need to move the logback config xml to the EAR? Is this a issue with how we are packaging our EARs? I can provide my logback config and other config if needed. Thanks, Chris

1 0