February 2012 - logback-user

Missing classfile with Filter Evaluator
by George, Kenneth V [NTK] 06 Feb '12

06 Feb '12

I am creating a filter for one of the appenders and I am getting this error: Exception in thread "main" java.lang.NoClassDefFoundError: org/codehaus/janino/ScriptEvaluator at ch.qos.logback.core.boolex.JaninoEventEvaluatorBase.start(JaninoEventEvaluatorBase.java:57) at ch.qos.logback.core.joran.action.NestedComplexPropertyIA.end(NestedComplexPropertyIA.java:167) at ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:318) at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:197) at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:183) at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:62) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:147) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:133) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:96) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:73) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:65) at ch.qos.logback.classic.net.SimpleSocketServer.configureLC(SimpleSocketServer.java:169) at ch.qos.logback.classic.net.SimpleSocketServer.main(SimpleSocketServer.java:67) Caused by: java.lang.ClassNotFoundException: org.codehaus.janino.ScriptEvaluator at java.net.URLClassLoader$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) ... 13 more I have attempted to look around and cannot find the class anywhere in the .jar files shipped with the product. Anyone know where it is? ________________________________ This e-mail may contain Sprint Nextel proprietary information intended for the sole use of the recipient(s). Any use by others is prohibited. If you are not the intended recipient, please contact the sender and delete all copies of the message.

4 4

Compiler selecting wrong Logger method
by Stein, Eric 06 Feb '12

06 Feb '12

I'm seeing a funny error when trying to write to logback. import org.slf4j.Logger; import org.slf4j.LoggerFactory; final String arg1 = "arg1"; final String arg2 = "arg2"; final String arg3 = "arg3"; LOGGER.debug("Hi {} {}", arg1, arg2); LOGGER.debug("Hi {} {} {}", new String[] { arg1, arg2, arg3 }); LOGGER.debug("Hi {} {} {}", arg1, arg2, arg3); The last line is giving this error message: The method debug(Marker, String, Object, Object) in the type Logger is not applicable for the arguments (String, String, String, String) I don't see why it isn't using the method whose signature is debug(String, Object[]), especially given that I'm not using a Marker. I'm running in Eclipse Indigo, and my classpath looks like this: logback-classic-1.0.0.jar logback-core-1.0.0.jar slf4j-api-1.6.4.jar Does anybody know why the compiler is using the wrong method? Thanks, Eric Stein _________________________________________________ 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 1

logback 1.0 - pickup config change & reconfigure
by Sean Kennedy 06 Feb '12

06 Feb '12

Hi, I'm trying to get logback to read an external config xml and "scan" it for changes, I've setup an entry in web.xml and done it via an include.. All looks good when I run it, change is detected in external file , but changes to fillter logging levels are ignored, in fact if I blank the entire external file it's also ignored !! >From ready various other posts this should be possible , it was fixed in 0.9.16 but perhaps I've missed something fundamental I've changed the filter up to ERROR and I still get INFO output !! Web.xml <env-entry> <env-entry-name>logback-file</env-entry-name> <env-entry-type>java.lang.String</env-entry-type> <env-entry-value>C:/logback_properties/localhost/logon.xml</env-entry-value> </env-entry> Logback.xml <configuration scan="true" scanPeriod="10 seconds" debug="true" > <insertFromJNDI env-entry-name="java:comp/env/logback-file" as="logback-file" /> <include file="${logback-file}" /> </configuration> Logon.xml [i.e. external file] <?xml version="1.0" encoding="UTF-8"?> <included> <appender name="A1" class="ch.qos.logback.core.rolling.RollingFileAppender"> <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>INFO</level> </filter> <File>C:/logs/localhost/logon.log</File> <encoder> <pattern>%d{ISO8601} %-5p %c - %m%n</pattern> </encoder> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>C:/logs/localhost/logon.log.%d</fileNamePattern> <maxHistory>2</maxHistory> </rollingPolicy> </appender> <root level="DEBUG"> <appender-ref ref="A1"/> </root> </included>

2 3

Creating logback logger programmatically
by Yusuf Soysal 03 Feb '12

03 Feb '12

Hello, I have a problem regarding to logback project. My requirement is I have to create log properties dynamically. Let me explain this by an example. My project creates socket communication with external system and it may have multiple sockets. For each socket, I want to have different log files which will contain the messages that is read and sent. To accomplish this, I create the logger for sockets programmatically. Problem is when I want to reconfigure loggers based on logback.xml (by adding scan="true" or by reinitializing the logback), the loggers I created becomes unusable. How can I fixed that or can you advise me another solution? This is my configuration file (logback.xml) <?xml version="1.0" ?> <configuration> <property name="HOME_PATH" value="/data/logs/myapp/" scope="CONTEXT" /> <property name="MYAPP_LOG_FILE" value="myapp.log" /> <property name="MYAPP_ROLLING_TEMPLATE" value="%d{yy-MM-dd}" scope="CONTEXT" /> <property name="MYAPP_OLD_LOG_FILE" value="${MYAPP_LOG_FILE}.%d{yy-MM-dd}" /> <property name="DEFAULT_PATTERN" value="%d{yyyy-MM-dd HH:mm:ss.SSS} [%file:%line] [%level] %msg%n" scope="CONTEXT" /> <appender name="myAppender" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>${HOME_PATH}${MYAPP_LOG_FILE}</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>${HOME_PATH}${MYAPP_LOG_FILE}.${MYAPP_ROLLING_TEMPLATE}</fileNamePattern> </rollingPolicy> <encoder class="ch.qos.logback.classic.encoder.PatternLayoutEncoder"> <pattern>${DEFAULT_PATTERN}</pattern> </encoder> </appender> <logger name="com.myapp" level="DEBUG" additivity="false"> <appender-ref ref="myAppender" /> </logger> <root level="OFF"> </root> </configuration> and here you can see how I create loggers programmatically (again, I do this only for socket logs). public static Logger createLogger(String name) { ch.qos.logback.classic.Logger templateLogger = (ch.qos.logback.classic.Logger) LogUtil.getLogger("com.myapp"); LoggerContext context = templateLogger.getLoggerContext(); String logDir = context.getProperty("HOME_PATH"); PatternLayoutEncoder encoder = new PatternLayoutEncoder(); encoder.setPattern(context.getProperty("DEFAULT_PATTERN")); encoder.setContext(context); DefaultTimeBasedFileNamingAndTriggeringPolicy<ILoggingEvent> timeBasedTriggeringPolicy = new DefaultTimeBasedFileNamingAndTriggeringPolicy<ILoggingEvent>(); timeBasedTriggeringPolicy.setContext(context); TimeBasedRollingPolicy<ILoggingEvent> timeBasedRollingPolicy = new TimeBasedRollingPolicy<ILoggingEvent>(); timeBasedRollingPolicy.setContext(context); timeBasedRollingPolicy.setFileNamePattern(logDir + name + ".log." + context.getProperty("MYAPP_ROLLING_TEMPLATE")); timeBasedRollingPolicy.setTimeBasedFileNamingAndTriggeringPolicy(timeBasedTriggeringPolicy); timeBasedTriggeringPolicy.setTimeBasedRollingPolicy(timeBasedRollingPolicy); RollingFileAppender<ILoggingEvent> rollingFileAppender = new RollingFileAppender<ILoggingEvent>(); rollingFileAppender.setAppend(true); rollingFileAppender.setContext(context); rollingFileAppender.setEncoder(encoder); rollingFileAppender.setFile(logDir + name + ".log"); rollingFileAppender.setName(name + "Appender"); rollingFileAppender.setPrudent(false); rollingFileAppender.setRollingPolicy(timeBasedRollingPolicy); rollingFileAppender.setTriggeringPolicy(timeBasedTriggeringPolicy); timeBasedRollingPolicy.setParent(rollingFileAppender); encoder.start(); timeBasedRollingPolicy.start(); rollingFileAppender.stop(); rollingFileAppender.start(); ch.qos.logback.classic.Logger logbackLogger = (ch.qos.logback.classic.Logger) LogUtil.getLogger(name); logbackLogger.setLevel(templateLogger.getLevel()); logbackLogger.setAdditive(false); logbackLogger.addAppender(rollingFileAppender); return logbackLogger; } And this is how I reinitialize logback private static void initializeLogback() { File logbackFile = new File(logFilePath); System.setProperty("logback.configurationFile", logbackFile.getAbsolutePath()); StaticLoggerBinder loggerBinder = StaticLoggerBinder.getSingleton(); LoggerContext loggerContext = (LoggerContext) loggerBinder.getLoggerFactory(); loggerContext.reset(); JoranConfigurator configurator = new JoranConfigurator(); configurator.setContext(loggerContext); try { configurator.doConfigure(logbackFile); } catch( JoranException e ) { throw new ColumbusRuntimeException(e.getMessage(), e); } } Note: I also posted the same question to stackoverflow: http://stackoverflow.com/questions/9060545/creating-logback-logger-programm…

1 0

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

JoranConfigurator + LoggerContext dont find classes
by Pepe Caballero 02 Feb '12

02 Feb '12

I am using joran Configurator to load muy logback.xml. I do this: LoggerContext context = (LoggerContext) LoggerFactory.getILoggerFactory(); JoranConfigurator configurator = new JoranConfigurator(); configurator.setContext(context); context.reset(); if (logbackfile != null) { InputStream fis = getServletContext().getResourceAsStream(logbackfile); configurator.doConfigure(fis); } In my integrated WebLogic Server it works perfect but when i deploy it in a production server it can find my classes that i configured in logback.xml as a evaluator. You can see on the end. It looks LoggerContext dont load class correctly. I have try to use ch.qos.logback.core.util.Loader.loadClass("util.log.LogSMTPEvaluator") and works perfectly but when i use ch.qos.logback.core.util.Loader.loadClass("util.log.LogSMTPEvaluator",context) it doenst works. ¿any idea please? ---------------------------------------------- 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 at at java.net.URLClassLoader$1.run(URLClassLoader.java:202) at at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at at java.lang.ClassLoader.loadClass(ClassLoader.java:247) at at ch.qos.logback.core.util.Loader.loadClass(Loader.java:123) at at ch.qos.logback.core.joran.action.NestedComplexPropertyIA.begin(NestedComplexPropertyIA.java:100) 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 -- View this message in context: http://old.nabble.com/JoranConfigurator-%2B-LoggerContext-dont-find-classes… Sent from the Logback User mailing list archive at Nabble.com.

1 1