- logback-user - mailman3.qos.ch

ContextDetachingSCL, because it does not implement any of the required ServletContextListener …. ?
by R. van Twisk 13 Apr '12

13 Apr '12

Hello, I am trying to deploy a application on a glassfish cluster and I am receiving this warning: [#|2012-04-13T13:35:34.223-0400|SEVERE|glassfish3.1.2|javax.enterprise.system.tools.admin.org.glassfish.deployment.admin|_ThreadID=25;_ThreadName=Thread-2;|Exception while invoking class com.sun.enterprise.web.WebApplication start method java.lang.Exception: java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: java.lang.IllegalArgumentException: java.lang.IllegalArgumentException: PW C1430: Unable to add listener of type: ch.qos.logback.classic.selector.servlet.ContextDetachingSCL, because it does not implement any of the required ServletContextListener, ServletContextAttributeLi stener, ServletRequestListener, ServletRequestAttributeListener, HttpSessionListener, or HttpSessionAttributeListener interfaces I am at a loss why I get this warning because ContextDetachingSCL implements ServletContextListener. So That can't be the issues. What else should I lookout for? Ries

1 0

RollingFileAppender - Current Log with No Date
by sdoca sdoca 13 Apr '12

13 Apr '12

Hi, Is it possible to set up a RollingFileAppender so that the current log file (i.e. today's) doesn't have a date as part of the filename? Then when the log rolls over, the date is appended to the filename similar to how log4j's DailyRollingFileAppender works? Thanks!

2 2

Setting MDCFilter values at runtime
by Dan Cripe 13 Apr '12

13 Apr '12

Hi- I'd like to leverage the MDCFilter TurboFilter, but I need to be able to change the "value" element at runtime. Basically, if a specific user is having trouble, I want to set their logs to show up as DEBUG while the remainder of the logs show up as INFO. Is there a way (preferably using JMX) that this can be done via configuration? If not, what's the best approach programatically? Thanks, Dan

3 5

SiftingAppender not working
by Y M 12 Apr '12

12 Apr '12

Hello, I had this code well tested when I wrote it months ago, but now it is failing. The only issue is the SiftingAppender: <appender name="SIFTING" class="ch.qos.logback.classic.sift.SiftingAppender"> <discriminator class="ch.qos.logback.classic.sift.MDCBasedDiscriminator"> <key>userId</key> <defaultValue>none</defaultValue> </discriminator> <sift> <appender name="SIFTING-${userId}" class="ch.qos.logback.core.rolling.RollingFileAppender"> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>${log_dir}/sifting/log.${userId}.%d{yyyy-MM-dd}.%i.log.zip</fileNamePattern> <maxHistory>30</maxHistory> <cleanHistoryOnStart>true</cleanHistoryOnStart> <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP"> <maxFileSize>25MB</maxFileSize> </timeBasedFileNamingAndTriggeringPolicy> </rollingPolicy> <encoder><pattern>%date %-5level %logger %X{userId} - %message%n%xThrowable{full}</pattern></encoder> </appender> </sift> </appender> It is simply not logging anything at all. The startup info is short, maybe indicating that it is not being properly initialized: 10:29:18,102 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[MAIN] - File property is set to [null]10:29:18,102 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.classic.sift.SiftingAppender]10:29:18,107 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [SIFTING]10:29:18,107 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting additivity of logger [package.project.x] to false...10:29:18,727 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to WARN10:29:18,727 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [MAIN] to Logger[ROOT]10:29:18,727 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [SIFTING] to Logger[package.project]10:29:18,727 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration. I was upgrading from logback 1.0 to 1.0.1 to use 'cleanHistoryOnStart' when I noticed this. I rolled back to 1.0, but nothing changed. Following other mails and messages around, I tried my RollingFileAppender by itself, and it works fine. The MDC is also fine, as it is printed in my other appenders. I also used <statusListener class="ch.qos.logback.core.status.OnConsoleStatusListener" /> , but nothing useful. Right now I have no idea how to proceed or how can I investigate this further.Any help is appreciated. Thanks!

2 4

Configuring custom logback logger and appender in Spring beans
by Goyal 22 Mar '12

22 Mar '12

Hey, I am a newbie to logback.Please excuse me if my question is silly. I have a project which uses slf4j and log4j for some kind of logging. Now I want to have logback configured for some logging to files keeping along with the previous log4j and slf4j mechanisms. I am trying to configure spring beans for logback appender and logback logger in application context and then the logger beans are autowired with other beans (as property) which are already configured.. I am having problem in creating bean which will have resulting class ch.qos.logback.classic.Logger. Anybody having suggestions on how this can be done? Thanks in advance :-) -- View this message in context: http://old.nabble.com/Configuring-custom-logback-logger-and-appender-in-Spr… Sent from the Logback User mailing list archive at Nabble.com.

1 0

DBAppender with JNDI, JTDS
by Stein, Eric 21 Mar '12

21 Mar '12

I'm playing around with DBAppender, trying to get it to work with my webapp. What I'm finding is that this will log to the database: <connectionSource class="ch.qos.logback.core.db.DriverManagerConnectionSource"> <driverClass>net.sourceforge.jtds.jdbc.Driver</driverClass> <url>MY_URL</url> <user>MY_USERNAME</user> <password>MY_PASSWORD</password> </connectionSource> but this won't: <connectionSource class="ch.qos.logback.core.db.JNDIConnectionSource"> <param name="jndiLocation" value="jdbc/MyDatabase" /> </connectionSource> Username and password are set in the datasource definition. The specific error I'm getting is: 13:15:52,470 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@28:14 - RuntimeException in Action for tag [appender] java.lang.IllegalStateException: DBAppender cannot function if the JDBC driver does not support getGeneratedKeys method *and* without a specific SQL dialect at java.lang.IllegalStateException: DBAppender cannot function if the JDBC driver does not support getGeneratedKeys method *and* without a specific SQL dialect I read a little about SQLDialect, but I appear to be missing the part that shows how to configure it, and there's no dialect for JTDS. Am I up the creek here, or is this possible? Thanks, Eric _________________________________________________ Don't gamble with your environmental information. Learn how the world's largest on-demand environmental information management system can help you mitigate your operating risk: www.locustec.com.

2 2

syslogappender stacktraces get cut
by Ingebrigt Berg 20 Mar '12

20 Mar '12

Hi ! We've recently made the switch from Log4j to Logback. We use Syslog to send logfiles to our logserver, and things generally work. But when there are stacktraces in the logs we get in trouble. SyslogAppender will replace lineshifts with '#011' to make the logentry a single line. Then it will cut each line that is to long according to the syslog limit of 2K/line. Only the fist segment will arrive in the correct log. The remaining segments do not contain everything in the suffixPattern, and our regexp will not have anything to match. The segment will end up in a 'trash' log for unmatchable loglines. My config for the SyslogAppender looks like this: <contextName>company-${CONTEXT_PATH}-${environment}</contextName> <appender name="LOGSERVER_FILE" class="ch.qos.logback.classic.net.SyslogAppender"> <syslogHost>localhost</syslogHost> <facility>local3</facility> <SuffixPattern>%contextName %d{dd.MM.yyyy HH:mm:ss.SSS} [%p] [%c{1}] [%X{ThreadId}]: %m%n</SuffixPattern> </appender> We use the contextName property to control the logfilename. On the receiving end we read the contextName parameter (using a regexp) for each log line, and write the line to a file with a corresponding name. We had a similar problem when we used Log4J (Where the Tag element was used in the same manner), and fixed it back then by writing a custom log4j SyslogAppender. But the main purpose of moving to Logback is to loose all our home brew logging stuff, we don't want to go down that path again. If we can't make Logback work out of the box with Syslog we'll probably end up going back to Log4J. (Another alternative is to replace Syslog with Gelf, but that's further down the road). However, I imagine Logback and Syslog being a common combination, and surely someone must have this working out of the box. Any advice will be appreciated. My requirements are simple: -must work with no custom logging code, only config (preferably xml) -stacktraces in logs must work -must be able to fully control the filename on the recieving end. cheers, Ingebrigt Berg

2 1

Appendere with timeBasedFileNamingAndTriggeringPolicy
by MarkIT 19 Mar '12

19 Mar '12

Hi everyone, I'm trying to create an appender with timeBasedFileNamingAndTriggeringPolicy but I got some trouble. I need to zip log files of previosly month in one .zip file (EX: on 04/01/2012 zip all file of March in one zip file). Here my logback.xml files: <configuration> <property scope="context" name="logFolder" value="log" /> <appender name="ROLLING" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>${logFolder}/myLog.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">  <fileNamePattern>${logFolder}/myLog.log-%d{yyyyMMdd}.%i.log.zip</fileNamePattern> <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP"> <maxFileSize>2MB</maxFileSize> </timeBasedFileNamingAndTriggeringPolicy> </rollingPolicy> <encoder> <pattern>%d{dd-MM-yyyy HH:mm:ss:SSS} [%thread] %-5level %logger{35} - %msg%n</pattern> </encoder> </appender> <root level="DEBUG"> <appender-ref ref="ROLLING" /> </root> </configuration> Where I'm wrong? In this way, it zip file when log name change to MyLog_20120319_0.log Thanks in advance -- View this message in context: http://old.nabble.com/Appendere-with-timeBasedFileNamingAndTriggeringPolicy… Sent from the Logback User mailing list archive at Nabble.com.

1 0

jmxConfigurator.objectName property replacement
by Nico Serfontein 16 Mar '12

16 Mar '12

Hi, I'm trying this flag in logback.xml: '<jmxConfigurator objectName="user:type=ngp,name=logging,instance=${com.sun.aas.instanceName},context=DEM" />' But the instance in jconsole is '${com.sun.aas.instanceName}' and not my cluster's name. How can I get around this? Regards, Nico

2 2

logback performance issue
by Jason Tang 13 Mar '12

13 Mar '12

Hi We use logback for debug log, and find it has performance problem. Here is the environment and traffic information: Config: - RollingFileAppender - Default encoder Traffic - 60~100 concurrent threads write debug log parallel - each time, the logback will record a short message (eg, trace information, method in/out) - several hundreds record per thread per seconds, which means several ten thousand records per second total in one JVM. - Compress log every 20M After running our application, we found the performance is poor, and IO, CPU is not the bottle neck, but check the stack, all threads is waiting on the *OutputStreamAppender.*subAppend(). *Linux 2.6.32.27-0.2.2.2501.1.PTF-default 03/14/12 _x86_64_ * *avg-cpu: %user %nice %system %iowait %steal %idle 12.82 0.00 2.20 0.43 0.00 84.55 Device: rrqm/s wrqm/s r/s w/s rsec/s wsec/s avgrq-sz avgqu-sz await svctm %util sda 0.00 415.50 0.00 9.50 0.00 3400.00 357.89 0.27 28.21 7.37 7.00 * I searched, and find some previous discuss ( http://mailman.qos.ch/pipermail/logback-user/2011-March/002211.html) and it is same situation we have here, and the suggestion is to "vote back" the "ImmediateFlush" and "BufferSize". So I wonder if it is a performance problem? or Configuration fault? When I check the IO stat, I notice the io package is small, and it is same as the behavior in OutputStreamAppender. So if it is the existed problem or limitation, can we have the flush control and buffer size configuration back? Although we try to have the socketAppender and have our owner buffer solution when writer to file, but we need to find out what's the real problem. BRs //Jason

2 1