- logback-user - mailman3.qos.ch

Shutting down async appenders, when using logback through slf4j
by Mads Bondo Dydensborg 13 Jun '13

13 Jun '13

Hi all I have a feeling that this is a FAQ, but my google-foo failed me. We provide an application that uses slf4j. The users configure it, in logback.xml, to use, among other things, an async appender. Tomcat complains about this, when redeploying or shutting down: SEVERE: The web application [/openformat] appears to have started a thread named [AsyncAppender-Worker-Thread-2] but has failed to stop it. This is very likely to create a memory leak. I found this issue/request: http://bugzilla.slf4j.org/show_bug.cgi?id=201 (Need ability to shutdown loggers and flush appenders), but it does not seem that this request has been honored. So, what is the recommended way to solve this? We would like to not hardcode the app to use logback (as it could potentially be used with log4j), but there seems to be no way to stop an async appender that the users have configured in? Thanks in advance. Mads -- Med venlig hilsen/Regards Chefarkitekt/Chief Architect cand.scient.dat, Ph.d., Mads Bondo Dydensborg Dansk BiblioteksCenter A/S, Tempovej 7-11, 2750 Ballerup, Tlf. +45 29 84 00 42

2 2

Localtime(from server) to be printed instead of GMT
by Kriti Wadhwa 13 Jun '13

13 Jun '13

Hello, As per my understanding currently using following pattern: <encoder> <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %class{0} %msg%n</pattern> </encoder> Time stamp printed in log files display time in GMT format by default. Using %date{HH:mm:ss.SSS,Australia/Perth} we can set the timezone to a particular value (In this case Australia/Perth). In my application I need: Time zone to be picked up from local server (/etc/localtime) where the application is running instead of setting it to a specific value in xml as shown above. How can I do this using logback.xml ? Please suggest. Thanks, Kriti =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you

4 5

Logback not rolling
by Steve Cohen 11 Jun '13

11 Jun '13

I have a logback configuration which specifies a daily rollover for a java swing application that is connected to a legacy backend and creates much log: <appender name="LocalFile" class="ch.qos.logback.core.rolling.RollingFileAppender"> <File>${logdir}/local.log</File> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">  <fileNamePattern>${logdir}/local.%d{yyyy-MM-dd}.log</fileNamePattern>  <maxHistory>10</maxHistory> </rollingPolicy> <encoder> <pattern>%d [%t] %-5p %c{2} - %m%n</pattern> </encoder> <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>INFO</level> </filter> </appender> I am finding in production that sometimes the logfile doesn't roll. I am not sure whether the application is running at the moment when it's supposed to roll, if that matters. Initially I suspected Windows 7 permissions - a bloody nightmare - were responsible. I initially thought that it always rolled correctly on some machines, but not on others. But now I find a case on a single machine where rollovers happened on some days but not on others. We are using logback v.1,0.7 and slf4j version 1.6.5. Yes, I know there are more recent versions but it would be a major hassle getting them deployed into our particular environment and I haven't seen this behavior in months of testing. Can anyone point me in a direction leading to the solving of this issue?

5 21

How to get list of configured loggers
by Govardhana 07 Jun '13

07 Jun '13

Hello, I am new to logback. I am migrating my project from log4j to logback. My question is How to get list of configured loggers into one object? Current code using log4j: Logger rootLogger =Logger.getRootLogger(); LoggerRepository currentRepository = rootLogger.getLoggerRepository(); currentRepository.resetConfiguration(); How i can use the same in logback? Thanks in Advance. Regards, Reddy -- View this message in context: http://logback.10977.n7.nabble.com/How-to-get-list-of-configured-loggers-tp… Sent from the Users mailing list archive at Nabble.com.

3 3

Problems with delete
by Steve Cohen 06 Jun '13

06 Jun '13

My previous thread showed me being successfully guided to a solution to rollover problems, by removing the File element of the rolling policy to avoid renaming issues. These problems surfaced in my instance due the following operational environment: 1) A GUI application running under Windows, not a server-side application. 2) Application is launched from time to time by different users. This leads to file-ownership issues preventing rename operation. Similar problems occur in the delete scenario based on the <maxHistory> element. But in this case, there is no workaround for deletion Also I wonder about this: TimeBasedArchiveRemover.cleanByPeriodOffset() calls java.io.File.delete(). File.delete() returns a boolean which is not checked in cleanByPeriodOffset(). It also throws a SecurityException (a RuntimeException) which isn't checked for. I'm not sure where this would be caught but I'm guessing it isn't the case here or we would have more catastrophic failures, so I suppose it's just returning false. Should logback do something about this? It's not clear because it's not clear what it could do. There is no alternative as in the case of renaming. Is there any solution available other than setting the directory so that every user has full rights to it? Mere write access is not enough in the Windows permissions scheme.

3 3

Blocked threads waiting for logback SiftingAppender on WebLogic
by Артём Тарасов 06 Jun '13

06 Jun '13

I have one problem with performance in production because of, as I think, blocked threads . When I got thread dumps from production environment I was surprised that about 50% of thread are in status: *-- Blocked trying to get lock: ch/qos/logback/classic/sift/SiftingAppender@0x1111fe3e8[unlocked]* At the same time, as you can see, SiftingAppender is 'unlocked'. I have no idea why it's happened. If we deep into logback sources we will find there a synchronized method which is the 'thin' place I think: ch.qos.logback.core.AppenderBase.doAppend(E) public synchronized void doAppend(E eventObject) { // WARNING: The guard check MUST be the first statement in the // doAppend() method. // prevent re-entry. if (guard) { return; } ... } We use weblogic v.10.3.5.0 slf4j.version - 1.7.5 logback.version - 1.0.13 Has anybody ideas why it's happened and how to avoid this problem? It may be not logback's problem. I now trying to find resolution only.

2 1

JaninoRuntimeException: Trying to add an auxiliary class
by diroussel 04 Jun '13

04 Jun '13

Hi, I've inherited an existing application. One of the first things I did was to move it from java.util.logging to logback using the excellent SLF4J migration tool. It works fine with an console appender, but when I try to use Janino in the logback.xml I run into trouble. When I add this to the logback.xml: <if condition='!property("myapp.log.dir").isEmpty()'> ... </if> Then I get "Failed to parse condition [!property("callisto.log.dir").isEmpty()] org.codehaus.janino.JaninoRuntimeException: Trying to add an auxiliary class "ch.qos.logback.core.joran.conditional.PropertyWrapperForScripts" while another class with the same name is already loaded". I've used this approach before, so I suspect it's something to do with GWT and the intellij GWT pluging doing something funny with the class loader. Has anyone seen this before, or got an idea where to start looking for a solution? There is a potention suggested fix here: http://jira.codehaus.org/browse/JANINO-159 But it requires a change in logback... if it's related. Thanks David P.S. Full stack trace below 11:59:24,293 |-ERROR in ch.qos.logback.core.joran.conditional.IfAction - Failed to parse condition [!property("callisto.log.dir").isEmpty()] org.codehaus.janino.JaninoRuntimeException: Trying to add an auxiliary class "ch.qos.logback.core.joran.conditional.PropertyWrapperForScripts" while another class with the same name is already loaded at org.codehaus.janino.JaninoRuntimeException: Trying to add an auxiliary class "ch.qos.logback.core.joran.conditional.PropertyWrapperForScripts" while another class with the same name is already loaded at at org.codehaus.janino.SimpleCompiler$AuxiliaryClassLoader.addAuxiliaryClass(SimpleCompiler.java:266) at at org.codehaus.janino.SimpleCompiler$AuxiliaryClassLoader.access$200(SimpleCompiler.java:245) at at org.codehaus.janino.SimpleCompiler.classToType(SimpleCompiler.java:346) at at org.codehaus.janino.ClassBodyEvaluator.addPackageMemberClassDeclaration(ClassBodyEvaluator.java:286) at at org.codehaus.janino.ClassBodyEvaluator.cook(ClassBodyEvaluator.java:212) at at org.codehaus.janino.SimpleCompiler.cook(SimpleCompiler.java:194) at at org.codehaus.commons.compiler.Cookable.cook(Cookable.java:80) at at org.codehaus.commons.compiler.Cookable.cook(Cookable.java:72) at at ch.qos.logback.core.joran.conditional.PropertyEvalScriptBuilder.build(PropertyEvalScriptBuilder.java:50) at at ch.qos.logback.core.joran.conditional.IfAction.begin(IfAction.java:67) at at ch.qos.logback.core.joran.spi.Interpreter.callBeginAction(Interpreter.java:275) at at ch.qos.logback.core.joran.spi.Interpreter.startElement(Interpreter.java:147) at at ch.qos.logback.core.joran.spi.Interpreter.startElement(Interpreter.java:129) at at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:50) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:149) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:135) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:99) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:49) at at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:75) at at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:148) at at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:85) at at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:55) at at org.slf4j.LoggerFactory.bind(LoggerFactory.java:128) at at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:107) at at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:295) at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:269) at at org.apache.commons.logging.impl.SLF4JLogFactory.getInstance(SLF4JLogFactory.java:156) at at org.apache.commons.logging.impl.SLF4JLogFactory.getInstance(SLF4JLogFactory.java:132) at at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351) at at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:270) at at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:112) at at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:543) at at org.mortbay.jetty.servlet.Context.startContext(Context.java:136) at at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1220) at at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:513) at at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:448) at at com.google.gwt.dev.shell.jetty.JettyLauncher$WebAppContextWithReload.doStart(JettyLauncher.java:468) at at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39) at at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) at at org.mortbay.jetty.handler.RequestLogHandler.doStart(RequestLogHandler.java:115) at at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39) at at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) at at org.mortbay.jetty.Server.doStart(Server.java:222) at at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39) at at com.google.gwt.dev.shell.jetty.JettyLauncher.start(JettyLauncher.java:672) at at com.google.gwt.dev.DevMode.doStartUpServer(DevMode.java:509) at at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:1068) at at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:811) at at com.google.gwt.dev.DevMode.main(DevMode.java:311) at at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at at java.lang.reflect.Method.invoke(Method.java:597) at at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120) -- View this message in context: http://logback.10977.n7.nabble.com/JaninoRuntimeException-Trying-to-add-an-… Sent from the Users mailing list archive at Nabble.com.

2 1

Can we have more then one varable in file name
by praveen patil 30 May '13

30 May '13

Hi everyone I am setting two variable in MDC and then in my appender in file tag i gave two variable ${configId} and ${threadName}. but when i run it i get only threadName value and for ${configId} it shows configId is UNDEFIND. but when the mdc context i found it is in the context, then why it giving error. <appender name="SIFT" class="ch.qos.logback.classic.sift.SiftingAppender"> <discriminator class="com.hotwaxmedia.logger.ThreadNameBasedDiscriminator"/> <sift> <appender class="ch.qos.logback.core.FileAppender"> <file>runtime/logs/DataManagerLog/${configId}-${threadName}.html</file> <layout class="ch.qos.logback.classic.PatternLayout"> <pattern><div class="%p">%d $${threadName} -%X{configId}$ [%logger{0} : %-5level] %msg%n%rEx</div></pattern> </layout> </appender> </sift> </appender> please help. Praveen

3 3

Splitting logback-access logs per application
by Xavier Dury 29 May '13

29 May '13

Hi, is it possible to split logback-access logfile per application with sifting (using something like ${contextName} in the filename)? Which discriminator should be used? Thanks, Xavier

1 0

How could i get the file path that i set in appender in logback
by praveen patil 29 May '13

29 May '13

Hi folks, How could i get the file path that i set in appender - the following is appender i am using. <appender name="SIFT" class="ch.qos.logback.classic.sift.SiftingAppender"> <discriminator class="com.hotwaxmedia.logger.ThreadNameBasedDiscriminator"/> <sift> <appender class="ch.qos.logback.core.FileAppender"> <file>runtime/logs/app-${threadName}.html</file> <layout class="ch.qos.logback.classic.PatternLayout"> <pattern><div class="%p">%d $${threadName}$ [%logger{0} : %-5level] %msg%n%rEx</div></pattern> </layout> </appender> </sift> </appender> please help. Thanx and regards praveen

1 0