March 2010 - logback-user - mailman3.qos.ch

Why is SMTPAppenderBase.setCharsetEncoding not public
by Andreas Dejung 21 Mar '10

21 Mar '10

Hi all Is there a specific reason why the SMTPAppenderBase.setCharsetEncoding method is not public. I'd like to call it but to do that need either to extend or have a class in the same package which I don't really want. Do I miss something ? Cheers Andy

2 2

Remove appender from SiftingAppender
by Matthias Kretschmar 17 Mar '10

17 Mar '10

Hi @ all, I have an application handeling commands. Every command is created, executed and deleted at the end. For this, I use a SiftingAppender, with the commandId from the MDC as discriminator. As I understand the concept of the SiftingAppender, it creates a new Appender (in my case FileAppenders that write to seperate folders) for every command, that is created. So far, so good. Now I want to delete my command, inclusive its working directory with its logs. There I get a exception, that the directory cannot be deleted, because files are still in use. I assume, that the logfile cannot be deleted, because the Stream of the FileAppender still is open. Is there a possibility to close the stream. I would prefer a solution, where the FileAppender is closed or detached only by use of slf4j-api. But I believe, that I also have to use logBack in my source code. Until now, I succeeded getting the SiftingAppender, but I couldn't get the FileAppender. Matthias

2 2

opposite of ThresholdFilter or LevelRangeFilter available?
by Christian Migowski 16 Mar '10

16 Mar '10

Hi, does logback offer some functionality that can be thought of the opposite of the ThresholdFilter, i.e. I want an appender to log only events with levels BELOW and equal to the level specified. With log4j, there is the org.apache.log4j.varia.LevelRangeFilter available that can do such things, does something similar exists in logback? thanks in advance, regards, christian!

2 1

PatternLayout example not working (%PARSER_ERROR_)
by Eric Ortéga 13 Mar '10

13 Mar '10

Hi, I tried to use PatternLayout in my application, by mimicking the code in the Chapter 5 of the manual (http://logback.qos.ch/manual/layouts.html#ClassicPatternLayout) and kept getting this kind of errors : %PARSER_ERROR_message%PARSER_ERROR_n I ended up trying to compile the exact same code as in the manual and in the PatternSample.java example, still getting the same output. Looking into the sources gave me the idea to set the context of the layout, which indeed solved the problem : PatternLayout layout = new PatternLayout(); layout.setContext(rootLogger.getLoggerContext()); // <= ADDED THIS LINE layout.setPattern("%-5level [%thread]: %message%n"); layout.start(); Before that, I searched a solution to this problem on the net and didn't find anything relating to it, so I figured I should leave a message here in case it can help others... I don't know if the problem originates from a bug in logback or a mistake in the manual, so I post in the user list. I think it should get fixed, at least in the manual, though. Cheers, Éric

1 0

SMTPAppender problem using gmail example
by Federico Schroder 10 Mar '10

10 Mar '10

Hello, I'm having problems trying to use the gmail example provided here: http://logback.qos.ch/manual/appenders.html My config is: ... <appender name="email" class="ch.qos.logback.classic.net.SMTPAppender"> <SMTPHost>smtp.gmail.com</SMTPHost> <SMTPPort>465</SMTPPort> <SSL>true</SSL> <Username>yyy(a)gmail.com</Username> <Password>xxx</Password> <To>zzz(a)gmail.com</To> <From>aaa(a)no-reply.com</From> <Subject>APP ERROR: %class{20} - %m</Subject>  <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>ERROR</level> </filter> <layout class="ch.qos.logback.classic.PatternLayout"> <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{1} - %msg%n</pattern> </layout> </appender> ... ... and I'm getting this in the log: 19:41:03,031 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@38:16 - no applicable action for [SMTPPort], current pattern is [[configuration][appender][SMTPPort]] 19:45:30,244 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@39:11 - no applicable action for [SSL], current pattern is [[configuration][appender][SSL]] 19:45:40,367 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@40:16 - no applicable action for [Username], current pattern is [[configuration][appender][Username]] 19:45:40,740 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@41:16 - no applicable action for [Password], current pattern is [[configuration][appender][Password]] Any suggestion on what could be wrong? Thanks, Federico

3 4

About MaxHitory
by okadam 09 Mar '10

09 Mar '10

Hello, I have a question about MaxHistory. Logback version is 0.9.18 I think that behavior of MaxHistory is wrong in some circumstances. The similar behavior exists in the other thread, but I seemed to have not been resolved. e.g.) ・technical question ・urgent explination issue Also, it is not registered in JIRA. I test following cases. Could you confirm it? And could you tell me that its performance is normal? First, I set following xml files. ・<FileNamePattern>logFile.%d{yyyy-MM-dd-HH-mm}.log</FileNamePattern> ・<MaxHistory>2</MaxHistory> Second, I start the application in the following order. However, there is no log file in the log Directory. 1. I start the application at [2010-03-09 10:00] In the log Directory, ・logFile.log ...OK 2. I restart the application at [2010-03-09 10:01] In the log Directory, ・logFile.log ・logFile.2010-03-09-10-00.log ...OK 3. I restart the application at [2010-03-09 10:02] In the log Directory, ・logFile.log ・logFile.2010-03-09-10-00.log ・logFile.2010-03-09-10-01.log ...OK 4. I restart the application at [2010-03-09 10:03] In the log Directory, ・logFile.log ・logFile.2010-03-09-10-01.log ・logFile.2010-03-09-10-02.log ...OK 5. I restart the application at [2010-03-09 10:05] In the log Directory, ・logFile.log ・logFile.2010-03-09-10-01.log ・logFile.2010-03-09-10-03.log ...NG (logFile.2010-03-09-10-01.log is not deleted.) 6. I restart the application at [2010-03-09 10:08] In the log Directory, ・logFile.log ・logFile.2010-03-09-10-01.log ・logFile.2010-03-09-10-03.log ・logFile.2010-03-09-10-05.log ...NG (logFile.2010-03-09-10-01.log is not deleted.) Here is my XML file: <configuration> <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <File>logFile.log</File> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern>logFile.%d{yyyy-MM-dd-HH-mm}.log</FileNamePattern>  <MaxHistory>2</MaxHistory> </rollingPolicy> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern>[%-5level][%d{yyyy-MM-dd HH:mm:ss}] %class - %msg%n</Pattern> </layout> </appender> <root> <level value="debug" /> <appender-ref ref="FILE"/> </root> </configuration> Regards, Masanao -- View this message in context: http://old.nabble.com/About-MaxHitory-tp27834946p27834946.html Sent from the Logback User mailing list archive at Nabble.com.

1 0

Log file permissions
by Hontvári József 08 Mar '10

08 Mar '10

I cannot discover why the log file created by logback has different permissions then another file created by the same Java process. I don't see anything special in Logback code, do I miss something? The log file is only readable by the user running the process. /var/lib/jddclient drwxr-s--- 2 jddclient adm 4096 2010-03-08 12:24 . drwxr-xr-x 58 root root 4096 2010-03-08 12:23 .. -rw-r--r-- 1 jddclient adm 103 2010-03-08 13:04 status.xml /var/log/jddclient drwxr-s--- 2 jddclient adm 4096 2010-03-08 12:24 . drwxr-xr-x 15 root root 4096 2010-03-08 12:25 .. -rw------- 1 jddclient adm 9811 2010-03-08 13:04 jddclient

2 2

filtering by logger name in logback console plugin
by Kearney, Joe 08 Mar '10

08 Mar '10

Hi, I'm trying to use the Logback Eclipse plugin, Eclipse 3.5.2, Logback Console plugin 1.1.0. Works a charm, until I try to write any more sophisticated filters than the only example of Level >= INFO and similar. I'm trying to filter to accept DEBUG messages from my code, but deny such messages from Spring, whose loggers are called "org.springframework...". I try the following and keep getting "The new expression is not correct." There is no error in the Eclipse error log or in the console. logger.contains("org.springframework") event.getLoggerName().contains("org.springframework") (Guessing types of these supplied variables from http://logback.qos.ch/manual/filters.html#evalutatorFilter.) Filtering on the message appears to be accepted by the config window: message.contains("org.springframework") But it doesn't apply any filtering to the logger name. (Here the logger name actually gets compacted to "o.s...." but trying other, non-compacted, segments of the name doesn't help either.) For now I can filter out things like "reating instance" or "bean", but that's hardly satisfactory. What am I doing wrong with the logger name/event? Thanks, Joe

2 3

Spawning threads w/ their own appender
by Al Bupp 06 Mar '10

06 Mar '10

Greetings Fellow Logback Users, I hoping that someone on this list can help me to understand why I'm seeing odd logging behavior in a servlet-based app I've written. No doubt I've mis-implemented some aspect of logback, but I don't know what it might be. Here's what I've got in braod strokes. A servlet app which accepts HTTP requests. The servlet contains some global configuration and app data, including backend DB credentials. The servlet has a logback appender defined in a xml file: <configuration> <appender name="CostingServlet" class="ch.qos.logback.core.rolling.RollingFileAppender">  <File>\\pusehk08\pvcost_devl$\costingservlet.log</File> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern>%-17d{yyyy-MMM-dd HH:mm} %-6r [%t] %-6p %c{3} - %m%n</Pattern> </layout> <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy"> <maxIndex>10</maxIndex> <FileNamePattern>\\pusehk08\pvcost_devl$\costingservlet.log.%i</FileNamePattern> </rollingPolicy> <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy"> <MaxFileSize>2MB</MaxFileSize> </triggeringPolicy> </appender> <root level="debug"> <appender-ref ref="CostingServlet"/> </root> </configuration> I have to deploy this servlet to a series of dev, test and prod servers all using the same identical WAR package, so there are actually 3 different xml files, a particular one of which gets loaded depending on the state of a runtime server variable. I load the specific config file when the servlet inializes using this java code: <code> protected void configLogger() { // set logging configuration LoggerContext lc = (LoggerContext) LoggerFactory.getILoggerFactory(); try { JoranConfigurator configurator = new JoranConfigurator(); configurator.setContext(lc); lc.reset(); configurator.doConfigure(logConfigFullPath.toString()); } catch (JoranException je) { StringBuffer errMsg = new StringBuffer(outAppName.toString()); errMsg.append("Error loading logging configuration file: "); errMsg.append(je.toString()); System.out.println(errMsg.toString()); je.printStackTrace(); } } </code> As a result of incoming HTTP requests the servlet starts a thread to handle the request. This request handling class needs to have logging to a separate log file for each request. Since the logs for the requests should be named uniquely, I use the following xml configuration: <configuration> <timestamp key="byMilliSecond" datePattern="yyyyMMMdd'T'HHmmssSSSS" /> <appender name="FILE" class="ch.qos.logback.core.FileAppender"> <File>\\pusehk08\pvcost_devl$\reqlog-${byMilliSecond}.log</File> <layout> <Pattern>%-17d{yyyy-MMM-dd HH:mm} %-6r [%t] %-6p %c{3} - %m%n</Pattern> </layout> </appender> <root level="debug"> <appender-ref ref="FILE" /> </root> </configuration> Again, there have to be 3 separate request logging config files, one for each runtime environment. In the request handling class I also invoke the manual configuration: <code> LoggerContext lc = (LoggerContext) LoggerFactory.getILoggerFactory(); try { JoranConfigurator configurator = new JoranConfigurator(); configurator.setContext(lc); lc.reset(); configurator.doConfigure(reqLogConfigPath); } </code> The problem is that this approach doesn't work too well because after configuring the request logger, the servlet log message end up going into the request log until recall its configLogger() method. Seems like I'm missing something here, probably something hiding in plain sight in the manual. Any insight into this will be greatly appreciated. Cheers, Al -- View this message in context: http://old.nabble.com/Spawning-threads-w--their-own-appender-tp27772903p277… Sent from the Logback User mailing list archive at Nabble.com.

1 0

Help Logback and postgreSQL
by Mohammad Haider 05 Mar '10

05 Mar '10

Hi, I have created three tables for logback according to documentation. I have the following config. file: <?xml version="1.0" encoding="UTF-8"?> <configuration debug="true" scan="true" scanPeriod="30 seconds"> <appender name="DB" class="ch.qos.logback.classic.db.DBAppender"> <connectionSource class="ch.qos.logback.core.db.DriverManagerConnectionSource"> <driverClass>org.postgresql.Driver</driverClass> <url>jdbc:postgresql://localhost:5432/tips_log</url> <user>postgres</user> <password>test</password> </connectionSource> </appender> <root level="debug"> <appender-ref ref="DB"/> </root> </configuration> In my code I have put simple logger.debug("DB test");. However, I did not see any log data in the tables. Can anyone please help about this issue? Why am I not getting any log data in the table? -- Thanks * Mohammad Firoj Haider*

3 10