- logback-user - mailman3.qos.ch

AUDIT Syslog facility problem
by Pradnya Gawade 28 Mar '11

28 Mar '11

Hi, I am trying to use "AUDIT" Syslog facility for logging some stuff but it threw an error saying its not a valid Syslog facility. If I look into ch.qos.logback.core.net.SyslogAppenderBase -> facilityStringToint method, I can see that the configured Syslog facility is not compared with the constant for AUDIT facility. I even checked with the new version 0.9.28 source code, its the same thing. Is this an issue that needs to be fixed in the logback? Thank you, Pradnya

1 0

ERROR: URL [jar:file:/something.jar!/logback.groovy] is not of type file
by Evgeny Goldin 25 Mar '11

25 Mar '11

Hi, I get the following error when my library starts. It uses Logback via SLF4J API and "logback.groovy"<https://github.com/evgeny-goldin/gcommons/blob/master/src/main/resources/lo…>is packed in the root of jar file. 20:36:58,117 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback.groovy] at [jar:file:/C:/Users/evgeny/.m2/repository/... /gcommons-0.5.3-SNAPSHOT.jar!/logback.groovy] 20:36:58,122 |-ERROR in ch.qos.logback.core.joran.spi.ConfigurationWatchList@139d891 - URL [jar:file:/C:/Users/evgeny/.m2/repository/../* gcommons-0.5.3-SNAPSHOT.jar!/logback.groovy*] is not of type file 20:36:58,401 |-INFO in ch.qos.logback.classic.gaffer.ConfigurationDelegate@b92dc2 - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender] 20:36:58,402 |-INFO in ch.qos.logback.classic.gaffer.ConfigurationDelegate@b92dc2 - Naming appender as [CONSOLE] I tracked it down to ConfigurationWatchList.convertToFile()<http://logback.qos.ch/xref/ch/qos/logback/core/joran/spi/ConfigurationWatch…>that raises this error. 1) Is it a bug that this an Ok jar-based URL is marked as an error? 2) Can I start up the library silently without those messages displayed? This is my main goal here. Thanks! Best regards, Evgeny evgeny-goldin.com

2 2

maxHistory doesnt delete older files properly
by Raman, Kalyan 25 Mar '11

25 Mar '11

Hi, We were using logback's 'ConsoleAppender' for couple of our projects which was working good. Recently we are trying to use the 'RollingFileAppender' with 'timeBasedFileNamingAndTriggeringPolicy' and class "ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP" and facing issues with the deleting of the older archived files. Issue is that it doesn't always delete files older than the max history period when there is considerable time gap between the logging events. I can see many people raising this issue but couldn't find any information that this is resolved in any particular release. We are using the 0.9.17 and 0.9.24 versions and this problem occurs in both the versions. Below are the appender configurations of both the projects with the logback release versions used. Project 1: ------------------------------------------------- Uses logback-core 0.9.17 <appender name="ROLLING_FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>/var/tmp/GcrDBS/test/dbs.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>/var/tmp/GcrDBS/test/dbs.log.%d{yyyy-MM-dd_HH-mm}.%i.gz</fileNamePattern> <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP"> <maxFileSize>500KB</maxFileSize> </timeBasedFileNamingAndTriggeringPolicy> <maxHistory>6</maxHistory> </rollingPolicy> <layout name="stdLayout" class="ch.qos.logback.classic.PatternLayout"> <Pattern>%d{MMM dd HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n</Pattern> </layout> </appender> Project 2: ------------------------------------------------- Uses logback-core 0.9.24 <appender name="ROLLING_FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>/var/tmp/GcrWFC/test/dbs.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>/var/tmp/GcrWFC/test/dbs.log.%d{yyyy-MM-dd_HH-mm}.%i.gz</fileNamePattern> <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP"> <maxFileSize>100KB</maxFileSize> </timeBasedFileNamingAndTriggeringPolicy> <maxHistory>5</maxHistory> </rollingPolicy> <encoder> <pattern>%d{MMM dd HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n</pattern> </encoder> </appender> Could someone please let me know if this is fixed in any release? And if so what is that? Or any work around for this? Thanks in advance. Kalyan -------------------------------------------------------------------------- NOTICE: Morgan Stanley is not acting as a municipal advisor and the opinions or views contained herein are not intended to be, and do not constitute, advice within the meaning of Section 975 of the Dodd-Frank Wall Street Reform and Consumer Protection Act. If you have received this communication in error, please destroy all electronic and paper copies and notify the sender immediately. Mistransmission is not intended to waive confidentiality or privilege. Morgan Stanley reserves the right, to the extent permitted under applicable law, to monitor electronic communications. This message is subject to terms available at the following link: http://www.morganstanley.com/disclaimers. If you cannot access these links, please notify us by reply message and we will send the contents to you. By messaging with Morgan Stanley you consent to the foregoing.

2 1

Possible issue with time based rolling policy when using format %d{yyyy-MM-dd-a}
by Christopher.White＠bbh.com 24 Mar '11

24 Mar '11

Hi all, My goal is to have my log file roll over twice a day (one to hold all AM logs, and one to hold all PM logs). Here is my configuration in logback.xml: <appender name="FILE" class=" ch.qos.logback.core.rolling.RollingFileAppender"> <file>/opt/apps/weblogs/TransactionReporting/TransactionReporting.log</file> <rollingPolicy class=" ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>/opt/apps/weblogs/TransactionReporting/TransactionReporting. %d{yyyy-MM-dd-a}.gz</fileNamePattern> </rollingPolicy> <encoder> <pattern>[%date] [%thread] [%level] [%mdc] [%logger:%method:%line]: %msg%n</pattern> </encoder> </appender> This configuration does result in the correct naming of archived log files (e.g. TransactionReporting.2011-03-22-AM.gz). However, the contents of the archived log files do not just contain half of the day's log entries. Whether the archived log file name ends in "...AM.gz" or "...PM.gz" these log files can contain log entries for both the morning and the evening. And, the same goes for the active log file (TransactionReporting.log). This active log file does not get archived when the time changes from AM to PM...so the log file contains log entries for both the morning and the evening. It seems as if the log file is rolling over only once a day, but I don't believe that it rolls over at the same time every day. Based on the modified date value on the archived files, it seems completely random as to when the file is actually rolled over. Any help or advice would be greatly appreciated. Thanks, Christopher White Sr. Programmer 1-617-772-2403 Christopher.White(a)bbh.com *************************** IMPORTANT NOTE*****************************-- The opinions expressed in this message and/or any attachments are those of the author and not necessarily those of Brown Brothers Harriman & Co., its subsidiaries and affiliates ("BBH"). There is no guarantee that this message is either private or confidential, and it may have been altered by unauthorized sources without your or our knowledge. Nothing in the message is capable or intended to create any legally binding obligations on either party and it is not intended to provide legal advice. BBH accepts no responsibility for loss or damage from its use, including damage from virus. ********************************************************************************

1 0

Rollingpolicy problem
by Yihya Hugirat 24 Mar '11

24 Mar '11

hello all, i have a problem (i think it is a problem) with the Rolling policy when i put the path for the over rolled files as the same one for the log files the rolling policy will not be activated but the log file keep growing. Note: i have used the example files that comes with logback. here is my logback.xml file: <configuration scan="true" scanPeriod="15 seconds"> <insertFromJNDI env-entry-name="java:comp/env/appName" as="appName" /> <contextName>${appName}</contextName> <jmxConfigurator /> <property file="Levels.properties" /> <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>${AGRESSO_LOG_FOLDER}/Agresso.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>Agresso.log_%d{yyyy-MM-dd}.%i</fileNamePattern> <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP"> <maxFileSize>3MB</maxFileSize> </timeBasedFileNamingAndTriggeringPolicy> </rollingPolicy> <encoder> <pattern>%date %-5level %logger{35} - %msg%n</pattern> </encoder> </appender> <logger name="org.rle.services" level="DEBUG" > <appender-ref ref="FILE" /> </logger> <logger name="org.rle.services.agresso" level="DEBUG" additivity="false"> <appender-ref ref="FILE" /> </logger> <root level="DEBUG">  </root> </configuration> -- إِنَّ الَّذِينَ يُحِبُّونَ أَنْ تَشِيعَ الْفَاحِشَةُ فِي الَّذِينَ آمَنُوا لَهُمْ عَذَابٌ أَلِيمٌ فِي الدُّنْيَا وَالآخِرَةِ وَاللَّهُ يَعْلَمُ وَأَنْتُمْ لا تَعْلَمُونَ My public key please use it when you contact me: هذا مفتاحي العام الرجاء أستخدامه عند الإتصال بي: 09BA B710 4B98 ECDA 8C0A 6CB1 2E1E CF88 6A12 F2C3

1 0

ContextListener
by Roy Cronise 23 Mar '11

23 Mar '11

How do you add a context listener in a groovy configuration? Roy

1 0

Equivalent of LogManager.getCurrentLoggers() ?
by James Morgan 23 Mar '11

23 Mar '11

Hi, I've recently started using LogBack with SLF4j instead of Log4J and have run into a problem. We currently have a simple servlet that gets deployed with all our running apps which allows us to change the Logging level and add loggers at runtime. Im currently trying to convert the current implementation to support LogBack with SLF4j and have run into problems. One of the core parts of the servlet gets all loggers in order to create a GUI where things can be controlled from. It uses this factory class to get all loggers, org.apache.log4j.LogManager.getCurrentLoggers(). I've looked through the code and online but have yet to find an alternative solution. Do you know if there is away to get all loggers simplar to the given factory methods? Or am i heading in the wrong directiopn with this, is there alternatives to find this informaiton out about current loggers? Thanks for any help you can provide. Cheers James

3 3

control Loglevels through an external property file
by Yihya Hugirat 22 Mar '11

22 Mar '11

hallo all, we are migrating our logging System from JUL to Logback, we are using galssfish as web container. We are interested in controlling the loglevels through an external property file like the one in galssfish, i have tried to setup something like this with the file property but i keep get a filenotfoundexception here is the property: <property file="Levels.properties" /> i have created a logfile with the name of the web app in the same place i have no problems with the paths. could anyone plz tell me what i'm doing wrong here Regards Huigrat -- إِنَّ الَّذِينَ يُحِبُّونَ أَنْ تَشِيعَ الْفَاحِشَةُ فِي الَّذِينَ آمَنُوا لَهُمْ عَذَابٌ أَلِيمٌ فِي الدُّنْيَا وَالآخِرَةِ وَاللَّهُ يَعْلَمُ وَأَنْتُمْ لا تَعْلَمُونَ My public key please use it when you contact me: هذا مفتاحي العام الرجاء أستخدامه عند الإتصال بي: 09BA B710 4B98 ECDA 8C0A 6CB1 2E1E CF88 6A12 F2C3

1 1

TimeBasedRollingPolicy - old logs present in current file
by Pradnya Gawade 20 Mar '11

20 Mar '11

Hi, I am trying with this for a long time but could not figure out the problem. My web application has to log to a log file but we want different category tags to be assigned to the logs from specific packages, although all log will go to the same physical log file. I create one appender per category with the required tag included in the encoder pattern. I have crated a filter per appender so it will only take the logs for that category and reject all other logs.Then I map the parent package of my web application source code with all the appenders that I have created for each category. I know this sounds complicated please bear with me. The category mapping I get in the logging is fine and as expected but I am facing other unexpected issue of files rolling over. I am using daily rollover policy. File gets rolled over properly but the current log file contains a copy of logs from archived file with new logs appended to it. I don't understand why it happens. I use o.9.20 version of logback. File rollover used to work fine before I categorized the log and when all the logs simply used to go to the same file without any category tagging associated. Please suggest what could be going wrong if you can think of some thing. Thanks in advance. My logback.xml looks like:  <appender name="LOGFILE-LPR" class="ch.qos.logback.core.rolling.RollingFileAppender"> <filter class="abc.log.LogFilterFacilityLPR"/> <file>${log.dir}.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">  <fileNamePattern>${log.dir}.%d{yyyy-MM-dd}.log</fileNamePattern>  <maxHistory>30</maxHistory> </rollingPolicy> <encoder> <pattern>%date{MM/dd HH:mm:ss} [%mdc{WEBAPP}] LPR %-5level %logger{25}:%L - %msg %n %ex{full}</pattern> </encoder> </appender>  <appender name="LOGFILE-USER" class="ch.qos.logback.core.rolling.RollingFileAppender"> <filter class="abc.log.LogFilterFacilityUSER"/> <file>${log.dir}.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">  <fileNamePattern>${log.dir}.%d{yyyy-MM-dd}.log</fileNamePattern>  <maxHistory>30</maxHistory> </rollingPolicy> <encoder> <pattern>%date{MM/dd HH:mm:ss} [%mdc{WEBAPP}] USER %-5level %logger{25}:%L - %msg %n %ex{full}</pattern> </encoder> </appender> . . . .  <logger additivity="false" name="org.akaza.openclinica"> <level value="${logLevel}" /> <appender-ref ref="LOGFILE-OTHER"/> <appender-ref ref="LOGFILE-LPR"/> <appender-ref ref="LOGFILE-USER"/> <appender-ref ref="LOGFILE-MAIL"/> <appender-ref ref="LOGFILE-AUTH"/> <appender-ref ref="LOGFILE-UUCP"/> <appender-ref ref="LOGFILE-AUTHPRIV"/> </logger>

4 5

Restricting JMX control certain loggers?
by Steve Davis 17 Mar '11

17 Mar '11

Is it possible to configure logback so that most loggers' levels are modifiable via JMX, but restrict manipulation of certain loggers? E.g., enable the JMX Configurator for the root logger, but disable it for specific loggers with additivity="false"? It appears that the <jmxConfigurator /> element can only appear at the top level of a <configuration> block. The goal, for my application, is to allow user control of logging in the field, for debugging, but not allow anyone to disable certain loggers that handle security-related events. Preferably, those loggers wouldn't even show up in as attributes in jconsole. (This is a Java desktop app, not web.)

2 1