- logback-user - mailman3.qos.ch

question reg. reading JNDI env entries
by Ravikanth Gangarapu 08 Jun '11

08 Jun '11

Hi, I am using logback-classic (0.9.28) for a web application running on tomcat 5.5. I am trying to read the JNDI env entry values using the <insertFromJNDI env-entry-name="java:comp/env/stderr-logging" as="stdErrLogging" /> tag in the logback.xml file. I have lots of env entry values that can be read from META-INF/context.xml file. For this specific example, my context.xml file has this. <context> .... <Environment name="stderr-logging" type="java.lang.String" value="true"/> .... But, this insertFromJNDI tags always says the entry value is null or empty. However, Once I am in a servlet code, new InitialContext().lookup("java:comp/env/stderr-logging") retrieves the correct value from context xml file. I looked in the JNDIUtil class from ch.qos.logback.classic.util package and the code throws error saying "javax.naming.NameNotFoundException: Name java:comp is not bound in this Context". Would somebody know how to read the environment entry values from the META-INF/context.xml file ? Thanks for help Ravi

2 4

using logback in an API w/o impacting other applications
by Richard Sand 07 Jun '11

07 Jun '11

Hi all, In an API I had to write for a client to interface with an COTS application, I used log4j to bridge to the COTS application's log capability. To totally isolate the usage of log4j in the API I created a wrapper around a Logger with its own Hierarchy. I'm wondering if there is an analogous mechanism for accomplishing this in logback. public final class AgentLogger { public static Hierarchy heirarchy = new Hierarchy(new RootLogger(Level.TRACE)); private Logger wl = null; /** * Private constructor * * @param name */ private AgentLogger (String name) { wl = heirarchy.getLogger(name); wl.setAdditivity(false); } Any advice appreciated. Thanks! Best regards, Richard Sand | CEO 239 Kings Highway East | Haddonfield | New Jersey 08033 | USA Mobile: +1 267 984 3651| Office: +1 856 795 1722| Fax: +1 856 795 1733 <http://www.skyworthttg.com/>

2 3

DBAppender issue
by Stephen Schaeffer 07 Jun '11

07 Jun '11

Hi all, I'm attempting to use the DBAppender, with the MySQL dialect. I am unable to actually put any records into my DB however. It seems that the culprit is that in DBAppenderBase:append, there is a call to subAppend, which is implemented either in Access, in which case it takes an AccessEvent as it's first argument, or in Classic, in which case it takes an ILoggingEvent as it's first argument. What it is actually passing is a LoggingEvent (no initial I) object, and so I'm getting ClassCastExceptions, and nothing in my DB. I'm assuming that someone out there has this working, and I'm just wondering what I'm doing wrong. Thanks for any help. Stephen Schaeffer ________________________________ This message may contain confidential information and is intended for specific recipients unless explicitly noted otherwise. If you have reason to believe you are not an intended recipient of this message, please delete it and notify the sender. This message may not represent the opinion of IntercontinentalExchange, Inc. (ICE), its subsidiaries or affiliates, and does not constitute a contract or guarantee. Unencrypted electronic mail is not secure and the recipient of this message is expected to provide safeguards from viruses and pursue alternate means of communication where privacy or a binding message is desired.

2 5

Logback logging to MySQL
by Stephen Schaeffer 03 Jun '11

03 Jun '11

Hi all, I am in the process of exploring logback so we can migrate our logging off of our current mishmash. As part of that I have been trying to configure to write to a MySQL database. In the configuration file I have this: <appender name="DB" class="ch.qos.logback.access.db.DBAppender"> <connectionSource class="ch.qos.logback.core.db.DriverManagerConnectionSource"> <driverClass>com.mysql.jdbc.Driver</driverClass> <url>jdbc:mysql://localhost:3306/test</url> <user>logback</user> <password>logback</password> </connectionSource> <insertHeaders>true</insertHeaders> </appender> <root level="DEBUG"> <appender-ref ref="STDOUT" /> <appender-ref ref="FILE" /> <appender-ref ref="DB" /> </root> And I've run the scripts to set up the tables in MySQL, and logback can apparently connect ok - if I change any of the parameters in the config I get errors about it not connecting. On the console and in the logfile I can see output as I would expect, but the DB remains empty. I'm using MySQL 5.1.51 on a Mac, for what that's worth. Stephen Schaeffer ________________________________ This message may contain confidential information and is intended for specific recipients unless explicitly noted otherwise. If you have reason to believe you are not an intended recipient of this message, please delete it and notify the sender. This message may not represent the opinion of IntercontinentalExchange, Inc. (ICE), its subsidiaries or affiliates, and does not constitute a contract or guarantee. Unencrypted electronic mail is not secure and the recipient of this message is expected to provide safeguards from viruses and pursue alternate means of communication where privacy or a binding message is desired.

2 2

Can we rename logback.xml to some application specific name
by Renuka Pathak 03 Jun '11

03 Jun '11

Hello, Can we rename logback.xml or logback-test.xml to any other name? If yes, how to do that. I tried searching this but was not successful, so asking this question here. Thanks in advance, Renuka

2 2

Logback configuration in Virgo OSGi container
by mvwinsen 31 May '11

31 May '11

Hi, i'm trying to get logback logging working in my Virgo OSGi container. Doing this i'm having some difficulties logging to the rootLogger. Virgo is delivered with a serviceability.xml (which is a renamed logback.xml file). I want to have 'one' logconfiguration (preferabably the serviceability.xml) used by all bundles inside the container. Therefore i've set the VM arg -Dlogback.configurationFile=./config/serviceability.xml. So that the default log configuration is read from that file. When i start the container i see that the logging configuration is setted by default to the ./config/serviceablity.xml (i can see this because i've set the debug to true in the configuration tag of the xml file). In that configuration i've set the root level to info (see file below): <configuration debug="true" scan="true"> <jmxConfigurator/> <appender name="GENERAL" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>./serviceability/logs/GeneralTest.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy"> <fileNamePattern>./serviceability/logs/General.%i.log</fileNamePattern> <minIndex>1</minIndex> <maxIndex>5</maxIndex> </rollingPolicy> <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy"> <maxFileSize>5MB</maxFileSize> </triggeringPolicy> <encoder> <pattern>%-5p %d{ISO8601} [%18.18t] %50.50c : %m%n</pattern> </encoder> </appender> <root level="INFO"> <appender-ref ref="GENERAL" /> </root> </configuration> The problem that i'm facing it that when i ask log4j-over-slf4j to get a logger via the code, then the bundle is falling back to the default configuration of logback (not the one set via the VM args, and therefore is logging console of my Eclipse environment. And nothing to the log file. org.apache.log4j.Logger log; log = Logger.getLogger("logger1"); log.error("test123"); The strange thing is that when i add the above descibed logback.xml configuration to the bundle where i'm trying to log (src/main/resources/logback.xml), then the root logger is linked to the logfile and de log line is outputted to the file. Does anyone has an idea what i'm doing wrong? My goal is to set the logconfigation once as VM arg and just call the Logger.GetLogger('id') of any bundle in the container and log the line to the root logger which is descibed in the logconfiguration. Thanks in advance, Mark -- View this message in context: http://old.nabble.com/Logback-configuration-in-Virgo-OSGi-container-tp31743… Sent from the Logback User mailing list archive at Nabble.com.

2 1

Problems with MDC's inheritance
by Lóránt Pintér 31 May '11

31 May '11

Hi, AFAIK, Log4J's MDC had no inheritance between threads -- this is a new feature introduced in Logback. However, when you are using thread pools, this new feature can cause a lot of trouble, especially when moving to Logback from a different logging system. Consider the following situation: you have a web application where you use the MDC to keep track of which user is logged in. You do certain things on the request processing thread. There are other certain things that you want to execute "in the background". You want to print the originating user's name in the logs for both "foreground" and "background" tasks. In such a case the Runnable's you place on the thread pool's queue need to take care of retaining the MDC from the originating thread. If you do this, and do this in every instance, no problem. However, it happens that you forget to do this. In such a case, with Log4J's non-inherited MDC, you would get no user name printed in the logs for background tasks, because your thread pool threads would not have anything in the MDC. That's not a good situation, but at least you can spot that there's something missing. OTOH, if you forget to retain the MDC manually with Logback, instead of no data you get false data in the logs. This is because thread pool threads are going to be created with random parent threads. These thread pool threads will then inherit the MDC from these threads, and *keep* the MDC. So future Runnables passed to these threads will print their starting thread's username. False data is worse than no data, so it would be nice to avoid this. Is there a way to make Logback's MDC inheritance configuratble? Like, in logback.xml you could set if you wanted to use InheritableThreadLocals or not. If that doesn't work, it might even be better to have no inheritance at all. What do you think? Regards, Lorant

3 4

logback.groovy or logback.xml class path not recognized in excutable jar
by Rathnadhar.K.V 31 May '11

31 May '11

Namasthe, I want to know how to set the class path context in executable jar so that logback can read the configuration file either logback.groovy or logback.xml. Apparently when we execute the java program out of executable jar, the system set class path is not recognized. Only the classpath set in the MANIFEST file is recognized. Due to this logback (logback.jar) cannot read the user defined configuration hence it falls back to default configuration that only sends the messages to console. I have created the executable jar for my project. I work out of Eclipse environment. In this IDE environment I have set the required class path. When I "run" or "debug" using Eclipse, logback works perfectly. But when I run the executable jar natively (java -jar abc.jar), logback falls back default configuration. Placing the configuration files in the /lib directory where the logback jars are present, does not help. How enable the logback to read the configuration files in executable jar? -- View this message in context: http://old.nabble.com/logback.groovy-or-logback.xml-class-path-not-recogniz… Sent from the Logback User mailing list archive at Nabble.com.

1 0

Doubt about multiple configurations
by Vitor Granzinoli Vellozo 31 May '11

31 May '11

Hi Logbackers, In my application, I need multiple configurations to generate multiple files. The first problem is, I have to use one logback configuration with no modifications (because we have to use a proprietary framework, it is a framework of our client), so I have to keep a main configuration. The second problem is, the business of my application needs more than 3 different logs, so I need at list one more Logback configuration where I can put more than one file appender. My question is: How can I have one more logback configuration that do not have any application dependencies. That can be read from a "Helper/Util" class without any help from the infrastruture (ex: Spring). Or, if anyone have another idea? Thanks a lot! Vitor

3 3

multiple apps deployed in Tomcat
by Nathaniel Auvil 30 May '11

30 May '11

I want to deploy multiple applications in Tomcat. Each one will include Logback jars. I need to have the log configuration file external to the war so i can change them on the fly. Is the "best" way to do this to have an init servlet in each application which loads from the filesystem? I can pass a system property on Tomcat startup which points to a "config" directory.

2 1