- logback-user - mailman3.qos.ch

PatternLayout feature request
by Arthur Blake 12 Jul '07

12 Jul '07

I'm using Logback on a new project. I like it a lot so far. Seems like a leaner, tighter log4j. Pretty easy to learn quickly because it is so similar to log4j in a lot of ways. I'd like to see a feature in the PatternLayout where I can show just the class name of the logger without its package prefix. For example, if I have a logger named com.mycompany.myapplication.myarea.Stuff I'd like a version of the %logger conversion word that just outputs "Stuff" (not "com.mycompany.myapplication.myarea.Stuff" or even "c.m.m.m.Stuff") Most of my classes are unique across package names, and I'd like my log output to be more concise in this way. I'm not worried about being confused by name collisions because my application is small enough that it's obvious what logger is involved in my log output. I've gotten around this so far by naming some of my logs with just the class name without it's package, but I'd rather have a PatternLayout conversion word or specifier to handle this. Forgive me if this feature is already in the PatternLayout, but I couldn't find it after looking pretty hard. Thanks Arthur ____________________________________________________________________________________ We won't tell. Get more on shows you hate to love (and love to hate): Yahoo! TV's Guilty Pleasures list. http://tv.yahoo.com/collections/265

2 1

LoggingEvent's argument array (Object[]) is not populated by constructor nor Logger
by Robert Christian 07 Jul '07

07 Jul '07

Hello, I need access to the logged Object[], which should be populated in the LoggingEvent as argumentArray. Unfortunately (a) Logger does not populate this via the setter method, and (b) the LoggingEvent constructor swallows this. I think this may be a bug. Regards, Rob

2 1

XMLWatchdog
by Robert Christian 07 Jul '07

07 Jul '07

Hello, Is there a configureAndWatch() feature in logback to support log property changes on-the-fly? Thanks, Rob

2 1

Logback Oracle problem.
by Søren Davidsen 23 Jun '07

23 Jun '07

Hi List, I am using logback 0.9.7, and having problems with getting logged into an Oracle database using the DBAppender. I am using c3p0 as a datasource like this, and the tables are created as per the provided .sql files from the distribution: <appender name="DATABASE" class="ch.qos.logback.classic.db.DBAppender"> <connectionSource class="ch.qos.logback.core.db.DataSourceConnectionSource"> <dataSource class="com.mchange.v2.c3p0.ComboPooledDataSource"> <driverClass>oracle.jdbc.OracleDriver</driverClass> <jdbcUrl>jdbc:oracle:thin:@xxx:yy:ZZ</jdbcUrl> <user>ppppp</user> <password>qqqqqq</password> <param name="acquireRetryAttempts" value="1" /> <param name="acquireIncrement" value="1" /> <param name="minPoolSize" value="1" /> <param name="maxPoolSize" value="2" /> <param name="maxConnectionAge" value="600" /> </dataSource> </connectionSource> </appender> It works very sporadic, only some log-statements are put into the database (I have not yet found any pattern in which), and exceptions are never put into logging_event_exceptions Is there something I need to do or something else I'm missing? Thanks, Soren

2 2

Q: Howto force flush before exiting
by Jason Buberel 20 Jun '07

20 Jun '07

Here is the behavior I currently observe: I am using an SMTPAppender to delivery logging messages to my Inbox. By default, the SMTPAppender implementation that comes with Logback will trigger the sending of an email (including all accumulated messages) upon receipt of an ERROR level logging message. As a result of the default behavior, you can end up in a situation where you generate 100 INFO level messages to the SMTPAppender and when your application exits, no email will have been sent. Those 100 INFO-level logging messages will be discarded. Here is the behavior I would like to achieve: I would like to implement an EventEvaluator or TriggerPolicy that would force the email to be sent at time of exit or termination. I know that overriding finalize() is not a reliable method of doing this, as there is no guarantee that the VM will actually call it. I did try using hivemodule's Discardable interface in a subclass of SMTPAppender, which I use elsewhere in my application, but ran into problems with class loaders and the like. Any suggestions on the best way to achieve this - guaranteed flush/send of the email message if there are any unsent events in the queue? -jason -- View this message in context: http://www.nabble.com/Q%3A-Howto-force-flush-before-exiting-tf3953809.html#… Sent from the Logback User mailing list archive at Nabble.com.

3 4

maven jetty logback
by Kevin S. Clarke 20 Jun '07

20 Jun '07

Hi, I want to use logback with the maven-jetty plugin but I don't seem to be able to find the right place to put the logback.xml file. I've read the jetty app by itself looks in the $JETTY_HOME/resources folder but $project/src/resources doesn't seem to work for the plugin. Any ideas? Thanks, Kevin

3 3

logback.xml location?
by John Y. Lim 20 Jun '07

20 Jun '07

I'm using jboss. Where do I put this file?

4 3

Unable to use ContextSelector
by Leonardo de Moura Rocha Lima 30 May '07

30 May '07

Hello, all. I've been trying to use a ContextSelector to achieve the behavior of JNDIContextSelector, but replacing JNDI lookups with MDC.get(). It did work and now I can have a new LoggerContext based on MDC. That way, I can have new configuration options based on MDC variables. I changed the StaticLoggerBinder implementation to use this new ContextSelector and the first context is correctly get and used. The problem that is stopping my progress is that I can't get to use more than one context. The StaticLoggerBinder.getLoggerFactory() is called once, and only once: in startup. After that, I can't change the ILoggerFactory that's inside the LoggerFactory, because it's static and only set in static { }. That way, when I need to switch contexts, even if I change the current context inside the ContextSelector, it won't be used by the LoggerFactory. I even reproduced the calls from ContextSelectorFilter so that I set/unset the current context, but no use. I thought about using a wrapper ILoggerFactory, but it feels wrong, because the JNDIContextSelector doesn't use anything else and is supposed to work. What am I doing wrong? How do I use ContextSelectors outside what's mentioned in logback manual? Leonardo de Moura Rocha Lima 55 11 3094.3939

1 0

DBAppender with ConnectionPool
by Klaus UNGER 30 May '07

30 May '07

Hello, I do have a "funny" problem - so far my understanding ... I have successfully configured LogBack and SLF4J with an DBAppender I have clients which do their logging via SocketAppender to a LogServer, which is intended to write the messages to the database. Everything (except Exceptions and MDC - see former posts) works fine, but when I added C3P0 Connection Pooling to the appender, like shown in the documentation and the examples, I do get the following StackTrace: java.lang.ExceptionInInitializerError at com.mchange.v2.naming.JavaBeanReferenceMaker.<clinit>(JavaBeanReferenceMaker.java:39) at com.mchange.v2.c3p0.impl.PoolBackedDataSourceBase.<clinit>(PoolBackedDataSourceBase.java:203) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at java.lang.Class.newInstance0(Unknown Source) at java.lang.Class.newInstance(Unknown Source) at ch.qos.logback.core.joran.action.NestedComponentIA.begin(NestedComponentIA.java:107) at ch.qos.logback.core.joran.spi.Interpreter.callBeginAction(Interpreter.java:259) at ch.qos.logback.core.joran.spi.Interpreter.startElement(Interpreter.java:126) at ch.qos.logback.core.joran.spi.Interpreter.startElement(Interpreter.java:110) at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:36) at ch.qos.logback.core.joran.spi.Interpreter.play(Interpreter.java:336) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:96) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:74) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:38) at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:24) at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:35) at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:46) at org.slf4j.impl.StaticLoggerBinder.initialize(StaticLoggerBinder.java:52) at org.slf4j.impl.StaticLoggerBinder.<init>(StaticLoggerBinder.java:44) at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:39) at org.slf4j.LoggerFactory.<clinit>(LoggerFactory.java:57) at com.mobilkom.cusi.logging.LoggingServer.<clinit>(LoggingServer.java:13) Caused by: java.lang.IllegalStateException: Logging factory implementation cannot be null. See also http://www.slf4j.org/codes.html#null_LF at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:75) at org.apache.log4j.Category.<init>(Category.java:52) at org.apache.log4j.Logger.<init>(Logger.java:22) at org.apache.log4j.Log4jLoggerFactory.getLogger(Log4jLoggerFactory.java:38) at org.apache.log4j.Category.getLogger(Category.java:56) at org.apache.log4j.Category.getLogger(Category.java:60) at com.mchange.v2.log.log4j.Log4jMLog.getMLogger(Log4jMLog.java:51) at com.mchange.v2.log.MLog.getLogger(MLog.java:145) at com.mchange.v2.log.MLog.<clinit>(MLog.java:72) For me, it looks like, while Configuring the LogServer, the Systems tries to instantiate the DBAppender, which itself tries to setup the connection-pool which has some logging statements inside it's C3P0-CodeBase. The LoggingSystem is yet not properly initialized (Logging factory implementation cannot be null. See also http://www.slf4j.org/codes.html#null_LF) looks like "the cat is chasing it's tail" ... any ideas, hints, explanations, etc. - greatly welcome kind regards Klaus :)

1 0

DBAppender Configuration Example
by Klaus UNGER 30 May '07

30 May '07

Hello, is there a configuration example, how one can use DBAppender for writing events in an Oracle DB (see "Bug 57") I tought, maybe the explizit usage of SQLDialect for Oracle would propably "solve" the problem ... but I didn't find an example, how to configure the explizit usage of an SQLDialect. any hints highly appreciated kind regards K:) Unger --------------------- Klaus UNGER, BSc Münzgasse 3/40+42 A-1030 Wien mobil: +43 (664) 4236046

1 0