January 2012 - logback-user

Re: [logback-user] Logback suddenly stopped logging
by Andreas Dejung 19 Jun '14

19 Jun '14

I had the same problem and I think I know why J Solaris does interrupt IO blocked thread which then causes the OutputStreamAppender to catch the IOException in line 218 (version 0.9.24). I actually run version 0.9.18 but this part has not change so I guess it will behave the same way. If we look at http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4385444 InterruptedIOException should not be required by platform specification (sol) And log4j https://issues.apache.org/bugzilla/show_bug.cgi?id=44157 InterruptedIOException ignored by log4j I think it should be solved the same why } catch (InterruptedIOException iioe){ //give the thread a changes to act on interruption and then carry on Thread.currentThread().interrupt(); } catch (IOException ioe) { // as soon as an exception occurs, move to non-started state // and add a single ErrorStatus to the SM. this.started = false; addStatus(new ErrorStatus("IO failure in appender", this, ioe)); } I could not find the jira entry mentioned in this thread therefore I write it here J BTY the jvm option -XX:-UseVMInterruptibleIO does prevent the interruption by solaris but that's only a workaround and not solving the problem ;) Cheers Andy

8 16

(Important) Dynamically change the scan period
by Yihya Hugirat 08 Apr '13

08 Apr '13

hi all, i have migrated to logback to be able to change the log levels dynamically. i'm testing it now with calssfish 3.01 and somehow it is not working when i change the levels in logback.xml there nothing happens. by deploying from netbeans i get the following: |-INFO in ch.qos.logback.classic.turbo.ReconfigureOnChangeFilter@11bfee0 - Will scan for changes in [[C:\Dokumente und Einstellungen\user_Home\Eigene Dateien\NetBeansProjects\WS-LDAP\build\web\WEB-INF\classes\logback.xml]] every 15 seconds. but when i change the levels in this file nothing happens Any help will be appreciated Hugirat -- إِنَّ الَّذِينَ يُحِبُّونَ أَنْ تَشِيعَ الْفَاحِشَةُ فِي الَّذِينَ آمَنُوا لَهُمْ عَذَابٌ أَلِيمٌ فِي الدُّنْيَا وَالآخِرَةِ وَاللَّهُ يَعْلَمُ وَأَنْتُمْ لا تَعْلَمُونَ My public key please use it when you contact me: هذا مفتاحي العام الرجاء أستخدامه عند الإتصال بي: 09BA B710 4B98 ECDA 8C0A 6CB1 2E1E CF88 6A12 F2C3

3 4

Websphere specific JMX configuration?
by Sumanth Donthi 12 Jun '12

12 Jun '12

How can we enable JMX for logback in WebSphere ? Currently do not see ch.qos.logback.classic.jmx.Configurator in jconsole though <jmxConfigurator/> tag exist in logback configuration file. logback 0.9.27 WebSphere 7.0 This is similar to one posted earlier -- http://www.qos.ch/pipermail/logback-user/2010-November/001886.html -Sumanth

4 6

SMTPAppender mail not sent (logback 1.0.0, JDK 1.5)
by Louis-Félix 03 May '12

03 May '12

Hi, I upgraded to logback 1.0.0 in a web application (tomcat 5, JDK 1.5), and the ERROR email are not sent anymore from the SMTPAppender. When I rollback my logback-core and logback-classic JARs to version 0.9.30, it's working again. I have a simple config: <appender name="courriel" class="ch.qos.logback.classic.net.SMTPAppender"> <smtpHost>smtp.xxx.xx.xx</smtpHost> <to>xxx(a)xxx.xx.xx</to> <from>no-reply.ti(a)xxx.xx.xx</from> <subject>Test</subject> <cyclicBufferTracker class="ch.qos.logback.core.spi.CyclicBufferTrackerImpl"> <bufferSize>25</bufferSize> </cyclicBufferTracker> <layout class="ch.qos.logback.classic.html.HTMLLayout"> <pattern>%date%level%thread%logger%line%message</pattern> </layout> </appender> I am using logback 1.0.0 with no problem in an other project (with JDK 1.6). Is there any known compatibility problem between logback 1.0.0 and JDK 1.5? Thanks, Louis-Félix

6 10

class & line conversion words not working
by Chris Cheshire 23 Feb '12

23 Feb '12

I have just upgraded to logback 1.0 (from 0.9.x), and now the conversion words for %class and %line just produce a question mark. My pattern layout is <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern>%date [%thread] %-5level %logger %n%n Class : %class%n Line : %line%n%n%message%n</Pattern> </layout> Prior to the update this was working and now it's not. Everything else in the layout displays as specified, except %class and %line. I do have the java compiler generating debug information too. Any suggestions? Chris

1 2

DBAppender and EJB managed transactions
by Henning Diederichs 03 Feb '12

03 Feb '12

Hi there, I think I found out, why I couldn't log in database as I described in December. I activated the status listener as mentioned in an earlier question concerning DBAppender like this: <statusListener class="ch.qos.logback.core.status.OnConsoleStatusListener" /> and got this exception from JBoss: ERROR in ch.qos.logback.classic.db.DBAppender[myDBAppender] - problem appending event java.sql.SQLException: You cannot set autocommit during a managed transaction! at java.sql.SQLException: You cannot set autocommit during a managed transaction! at at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.setJdbcAutoCommit(BaseWrapperManagedConnection.java:878) at at org.jboss.jca.adapters.jdbc.WrappedConnection.setAutoCommit(WrappedConnection.java:712) at at ch.qos.logback.core.db.DBAppenderBase.append(DBAppenderBase.java:90) at at ch.qos.logback.core.UnsynchronizedAppenderBase.doAppend(UnsynchronizedAppenderBase.java:88) at at ch.qos.logback.core.spi.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:64) at at ch.qos.logback.classic.Logger.appendLoopOnAppenders(Logger.java:285) at at ch.qos.logback.classic.Logger.callAppenders(Logger.java:272) at at ch.qos.logback.classic.Logger.buildLoggingEventAndAppend(Logger.java:473) at at ch.qos.logback.classic.Logger.filterAndLog_0_Or3Plus(Logger.java:427) at at ch.qos.logback.classic.Logger.error(Logger.java:574) The transaction is handled by the EJB container and cannot be managed by DBAppenderBase line 90. I also tested the DBAppender in a web project that only uses Servlets and no EJBs. I could manage to log with the same log file. Is this a known issue? There has to be a possibility to log to DB without managing the transaction. Best if logback itself finds out, if managing transactions manually is allowed or not. Regards, Henning

1 1

Questions about SLF4JBridgeHandler
by cowwoc 30 Jan '12

30 Jan '12

Hi, I've got three questions: 1. http://www.slf4j.org/legacy.html mentions LevelChangePropagator but http://www.slf4j.org/api/org/slf4j/bridge/SLF4JBridgeHandler.html does not. Is it possible to add this to the Javadoc? 2. Why doesn't SLF4JBridgeHandler.install() register the listener automatically? 3. I've noticed that invoking SLF4JBridgeHandler.install() is not enough. You must remove any existing JUL handlers using: java.util.logging.Logger rootLogger = java.util.logging.LogManager.getLogManager().getLogger(""); java.util.logging.Handler[] handlers = rootLogger.getHandlers(); for (int i = 0; i < handlers.length; i++) { rootLogger.removeHandler(handlers[i]); } before invoking SLF4JBridgeHandler.install(). Shouldn't SLF4JBridgeHandler offer a method for doing it on behalf of the user? Thanks, Gili -- View this message in context: http://old.nabble.com/Questions-about-SLF4JBridgeHandler-tp33221503p3322150… Sent from the Logback User mailing list archive at Nabble.com.

1 0

Tomcat log problem
by James Annesley 26 Jan '12

26 Jan '12

Hi I am using logback 1.0 with a tomcat web app. I can get the logger writing to console nicely. I cannot get my web app specific logback.xml to be read however. I had log4j working OK on this system previously. Using Logback-access it works but is this the only way? Can anyone help? James

2 1

Class not found exception for Evaluator
by Pepe Caballero 26 Jan '12

26 Jan '12

I generated a smtp appender with my evaluator. in logBack.xml I have <appender name="Email" class="ch.qos.logback.classic.net.SMTPAppender"> <evaluator class="util.log.LogSMTPEvaluator"/> <smtpHost>${correo.name.direccionSMTP}</smtpHost> <to>${correo.name.to}</to> <from>${correo.name.from}</from> <username>${correo.name.usuario}</username> <password>${correo.name.clave}</password> <layout class="ch.qos.logback.classic.html.HTMLLayout"> <pattern>%d{yyyy-MM-dd HH:mm:ss}==> %m%n</pattern> </layout> </appender> When I deploy in integrated Weblogic Server with Jdeveloper11 it works fine. But, when i generated ear and deploy over my Weblogic Server i get: 12:32:57,830 |-ERROR in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Could not create component [evaluator] of type [util.log.LogSMTPEvaluator] java.lang.ClassNotFoundException: util.log.LogSMTPEvaluator at java.lang.ClassNotFoundException: util.log.LogSMTPEvaluator My aplication.ear have: - model.jar - logback-access-1.0.0.jar - logback-classic-1.0.0.jar - logback-core-1.0.0.jar - anothers jar libraries - view.war logback.xml is in view.war/WEB-INF/log-back.xml and util.log.LogSMTPEvaluator in model.jar. LogBack is initialize in a servlet init in view.war Any idea? -- View this message in context: http://old.nabble.com/Class-not-found-exception-for-Evaluator-tp33187958p33… Sent from the Logback User mailing list archive at Nabble.com.

1 1

TimeBasedFileNamingAndTriggeringPolicy writes to many files after restart
by Curtis Porter 23 Jan '12

23 Jan '12

While doing some testing I've encountered a situation where we generate a large number of log files. They seem to be rotating as expected, except for directly after a restart of the application. When that happens, logback writes a few messages to each file, starting at index 101 until it reaches the current file, at which point it resumes working normally. For example, the logs should rotate each month, and grow up to 10MB before rotating. As each rotates its log index will increase (2012-01.1.log, 2012-01.2.log, ..., 2012-01.891.log). logback is writing the first few messages to 2012-01.101.log and then walks up each log after that, writing a few log messages before moving on (presumably "realizing" that each log is at its size threshold). I'm puzzled that it starts at 2012-01.101.log (2012-01.1.log would make more sense). It's even more puzzling that it writes anything to the lower logs in the first place. Any ideas why this is happening? Here is my configuration: <configuration debug="false"> <turboFilter class="ch.qos.logback.classic.turbo.MarkerFilter"> <Marker>ALWAYS</Marker> <OnMatch>ACCEPT</OnMatch> </turboFilter> <appender name="R" class="ch.qos.logback.core.rolling.RollingFileAppender"> <prudent>true</prudent> <encoder> <Pattern>%d %p [%t] %X{user} %X{session} %F:%L - %m%n</Pattern> </encoder> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern>${catalina.home}/logs/tomcat.%d{yyyy-MM}.%i.log</FileNamePattern> <TimeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP"> <maxFileSize>10MB</maxFileSize> </TimeBasedFileNamingAndTriggeringPolicy> <maxHistory>2</maxHistory> </rollingPolicy> </appender> <logger name="org.apache.catalina.startup.Catalina" level="INFO" /> <root level="warn"> <appender-ref ref="R"/> </root> </configuration>

1 0