- logback-user - mailman3.qos.ch

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

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

Project Can't Find logback.xml file
by Roger Spears 23 Jan '12

23 Jan '12

Hello, I'm running Netbeans 7.0.1 on a Mac Book Pro with OS Lion. I'm currently using log4j without any problems. I wanted to try out logback. Yesterday I downloaded logback and placed the 4 jar files in the proper location. I'm able to run the basic logback HelloWorld example. Here's the code for the HelloWorld example I'm working with: package helloworld; import org.slf4j.Logger; import org.slf4j.LoggerFactory; public class HelloWorld { public static void main(String[] args) { Logger logger = LoggerFactory.getLogger("helloworld"); logger.debug("Hello world."); } } Here's my customized logback.xml file: <configuration> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <encoder> <pattern>%date %n [%thread] %level %logger{35} - %n %msg</pattern> </encoder> </appender> <root level="DEBUG"> <appender-ref ref="STDOUT" /> </root> </configuration> The problem is...Netbeans (or java) never picks up on my customized logback.xml file. I'm starting out easy by just changing the pattern to see if I can get it to work. When I run the project, I see the following on the console: 11:56:33.569 [main] DEBUG helloworld - Hello world. That's not the pattern I specified in logback.xml. I'm assuming I just don't have it in the proper location. I have a copy of logback.xml in the following locations just to see if I had it in the wrong place: NetBeansProjects -> HelloWorld -> src -> logback.xml NetBeansProjects -> HelloWorld -> logback.xml NetBeansProjects -> HelloWorld -> nbproject -> private -> logback.xml NetBeansProjects -> HelloWorld -> build -> classes -> logback.xml System -> Libraries -> Java -> Extensions -> logback.xml I am still unable to get the pattern I'm looking for. Does anyone know why this would be happening? Thanks, Roger -- Roger

3 12

SMTPAppender+Evaluator+Discriminator. ¿what buffer is send?
by Pepe Caballero 23 Jan '12

23 Jan '12

I am trying to send specifing error generated for some hours of day. So I decided to extends some class 1. First i implements Evaluator do decide when to send de email. It works correctly. 2. Second, i implement Discriminator interface to generate 2 buffers, One for the messaged generated on the hours that must not sended and another one for the messaged that must be sended by email. My problems is how SMTPAppender decide what buffer must be sended. Always looks to be sended the first called. ¿any idea? Thanks too much -- View this message in context: http://old.nabble.com/SMTPAppender%2BEvaluator%2BDiscriminator.-%C2%BFwhat-… Sent from the Logback User mailing list archive at Nabble.com.

1 1

Custom LayoutWrappingEncoder question
by Adam Gordon 18 Jan '12

18 Jan '12

I'm using a custom LayoutWrappingEncoder to colorize and selectively timestamp my log file entries. This encoder is configured via the <encoder> element in my logback XML file. My question is, with a custom encoder, is there a way I can specify a <layout> element in my <encoder> element and use the built in layout patterns? I've tried: <encoder class="com.bar.foo.CustomLayoutWrappingEncoder"> <layout class="ch.qos.logback.classic.PatternLayout"> [level] - %logger{15}: %message%n x%Ex{full} </layout> </encoder> But I'm seeing the following error in the console when testing that: 13:06:58,318 |-ERROR in ch.qos.logback.classic.PatternLayout("null") - Empty or null pattern. Am I doing this correctly? Thanks, --adam

3 7