- logback-user - mailman3.qos.ch

Help needed for File inclusion in logback with relative path
by Renuka Pathak 22 Aug '11

22 Aug '11

> > Hi All, > > I am looking for help in including outside file in logback.xml. It works > when I use absolute path but does not work when I use relative path. I am > using logback version 0.9.20. Below is the suedo code I am writing. > LOGBACK_FILE_PATH is defined in env.properties. I also tried with <include > resource=" "> but it does not work either. > > <configuration> > <property resource="env.properties" /> > <include file="${LOGBACK_FILE_PATH}/backendlogback.xml"/> > > </configuration> > > Any help is appreciated. > > Thanks & Regards, > Renuka >

2 1

SyslogAppender failing silently
by Daniel Serodio (lists) 19 Aug '11

19 Aug '11

I'm trying to setup SyslogAppender to log to a virtual machine that's running rsyslog, and because of a firewall rule on the VM, SyslogAppender wasn't connecting to rsyslog, but I didn't see any errors or warnings from Logback, even after setting a OnConsoleStatusListener. If I change the "syslogHost" parameter to a non-existing name, I get an error message on the console, but the same doesn't happen for a refused connection. I expected to see some sort of notification about this problem. Regards, Daniel Serodio

4 4

help needed for File inclusion in logback with relative path
by Renuka Pathak 19 Aug '11

19 Aug '11

Hi All, I am looking for help in including outside file in logback.xml. It works when I use absolute path but does not work when I use relative path. I am using logback version 0.9.20. Below is the suedo code I am writing. LOGBACK_FILE_PATH is defined in env.properties. I also tried with <include resource=" "> but it does not work either. <configuration> <property resource="env.properties" /> <include file="${LOGBACK_FILE_PATH}/backendlogback.xml"/> </configuration> Any help is appreciated. Thanks & Regards, Renuka

1 0

All error in a separate file
by DECHOUX Bertrand 19 Aug '11

19 Aug '11

Hi, I am new to logback configuration. I have read the online manual but clearly not in depth. I would like to log in a separate file all ERROR logs but keep these logs at the same time where they are supposed to be. I understand I could use root with an ERROR level and a file appender but then I woul lose all the details (logs lower than ERROR). Is there any obvious way that I might have missed? Regards, Bertrand Dechoux

2 1

Integration with Tomcat 7 with SLF4J & Logback
by Jun Victorio 15 Aug '11

15 Aug '11

I've noticed that the latest slf4j & logback have a problem integrating with latest tomcat 7 release. I know also there is third party that tried to solve this problem (https://github.com/grgrzybek/tomcat-slf4j-logback) I'm just wondering if you plan to fix this issue in the future. Thanks. Jun Victorio Starcom Computer Corp. 21520 30th Dr. SE, Suite 101 Bothell, WA 98021 425.486.6464 x209

2 2

Best practices for FATAL errors...
by Leon Rosenberg 15 Aug '11

15 Aug '11

Hi, since logback doesn't support log level FATAL I'm wondering how you guys are separating between 'normal' errors and 'really bad' errors. Example: Warning: tried to insert statement into db, found key conflict, resolved it (somehow). Normal errors: couldn't insert the statement into db because the encoding is invalid (or couldn't read user's file because its corrupt) - affects one user. Really bad errors: have no connection to db, so my further existence is rather meaningless. So how do you guys log fatal errors without fatal? .-) best regards Leon

5 6

AUTO: Manfred Kuhlmann is out of office. (Rückkehr am 29.08.2011)
by manfred.kuhlmann＠steria-mummert.de 08 Aug '11

08 Aug '11

Ich werde ab dem 06.08.2011 nicht im Büro sein. Ich kehre zurück am 29.08.2011. I will be out of the office starting 06.08.2011. I will be back on 29.08.2011. Ihre Nachricht werde ich nach meiner Rückkehr beantworten. I will answer your message after my return. Bitte Ihre Ansprechpartner in der Mitarbeiterdatenbank unter dem Reiter 'Abwesenheitsvertreter' eingeben (s.a. Hilfe-Button). Mit freundlichen Grüßen Best regards Manfred Kuhlmann Hinweis: Dies ist eine automatische Antwort auf Ihre Nachricht "Re: [logback-user] Connection leaks with DBAppender and GlassFish?" gesendet am 08.08.2011 13:54:13. Diese ist die einzige Benachrichtigung, die Sie empfangen werden, während diese Person abwesend ist. Steria Mummert Consulting AG Vorsitzender des Aufsichtsrates: Jürgen Sponnagel - Vorstand: Oliver Nazet (Vors.), Dr. Reinhard Liedl, Dr. Fritz Moser Gesellschaftssitz: Hamburg - HR B 61 116 Amtsgericht Hamburg - USt-ID-Nr.: DE118671351 Bitte denken Sie an Ihre Verantwortung gegenüber der Umwelt: Jede ausgedruckte E-Mail verursacht ca. 0,3 Gramm CO2 pro Seite. Diese Nachricht kann vertrauliche Informationen enthalten und ist allein für den Adressaten bestimmt. Wenn Sie nicht der rechtmäßige Empfänger sind, sind der Zugriff, die Weiterleitung, das Kopieren, die Veröffentlichung oder anderweitige Verwendung des Inhalts untersagt. In diesem Fall bitten wir Sie, den Absender unverzüglich zu informieren und diese E-Mail sowie sämtliche Kopien dieser E-Mail zu löschen. Der Inhalt von E-Mails innerhalb des Netzwerks kann überprüft werden, um die Übereinstimmung mit den geltenden Firmenrichtlinien und Vorgehensweisen zu gewährleisten. E-Mails können auf dem Transportweg von Dritten verändert werden, so dass deren Vollständigkeit und Echtheit nicht garantiert werden können. This e-mail communication may contain confidential information and is intended only for the recipient. If you are not the intended recipient you are not allowed to read, copy, distribute, publicize or use the content of this e-mail in any way. Please notify the sender and delete the e-mail and any copies of it. The content of e-mails within our network may be monitored to ensure compliance with company policies and procedures. E-mails can be alterated by third parties in transit. Therefore any e-mail is susceptible to alteration and its integrity cannot be assured.

1 0

Connection leaks with DBAppender and GlassFish?
by Stephan Vollmer-2 08 Aug '11

08 Aug '11

Hi, I use Logback 0.9.29 and the DBAppender to log error messages into a database. The Java EE 6 application runs with GlassFish 3.1 and uses the JNDIConnectionSource to obtain a database connection. I have created a separate database connection pool within GlassFish that is only used for Logback. This pool also has connection leak detection enabled. When the connection leak timeout has passed, the server log has the following error message: [#|2011-07-25T12:18:26.217+0200|INFO|glassfish3.1.1|javax.enterprise.resource.resourceadapter.com.su n.enterprise.resource.pool|_ThreadID=24;_ThreadName=Thread-2;|Reclaiming the leaked connection of pool [ loggerPool ] and destroying it so as to avoid both the application that leaked the connection and any other request that can potentially acquire the same connection from the pool end up using the connection at the same time|#] [#|2011-07-25T12:18:27.841+0200|WARNING|glassfish3.1.1|javax.enterprise.resource.resourceadapter.com .sun.enterprise.resource.pool|_ThreadID=24;_ThreadName=Thread-2;|A potential connection leak detected for connection pool loggerPool. The stack trace of the thread is provided below : com.sun.enterprise.resource.pool.ConnectionPool.setResourceStateToBusy(ConnectionPool.java:324) com.sun.enterprise.resource.pool.ConnectionPool.getResourceFromPool(ConnectionPool.java:758) com.sun.enterprise.resource.pool.ConnectionPool.getUnenlistedResource(ConnectionPool.java:632) com.sun.enterprise.resource.pool.ConnectionPool.internalGetResource(ConnectionPool.java:526) com.sun.enterprise.resource.pool.ConnectionPool.getResource(ConnectionPool.java:381) com.sun.enterprise.resource.pool.PoolManagerImpl.getResourceFromPool(PoolManagerImpl.java:242) com.sun.enterprise.resource.pool.PoolManagerImpl.getResource(PoolManagerImpl.java:167) com.sun.enterprise.connectors.ConnectionManagerImpl.getResource(ConnectionManagerImpl.java:338) com.sun.enterprise.connectors.ConnectionManagerImpl.internalGetConnection(ConnectionManagerImpl.java:301) com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:190) com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:165) com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:160) com.sun.gjc.spi.base.DataSource.getConnection(DataSource.java:113) ch.qos.logback.core.db.JNDIConnectionSource.getConnection(JNDIConnectionSource.java:69) ch.qos.logback.core.db.ConnectionSourceBase.discoverConnnectionProperties(ConnectionSourceBase.java:47) ch.qos.logback.core.db.JNDIConnectionSource.start(JNDIConnectionSource.java:54) ch.qos.logback.core.joran.action.NestedComplexPropertyIA.end(NestedComplexPropertyIA.java:167) ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:315) ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:194) ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:180) ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:52) ch.qos.logback.core.joran.spi.Interpreter.play(Interpreter.java:332) ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:132) ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:93) ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:52) ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:77) ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:150) ch.qos.logback.classic.selector.ContextJNDISelector.getLoggerContext(ContextJNDISelector.java:108) org.slf4j.impl.StaticLoggerBinder.getLoggerFactory(StaticLoggerBinder.java:108) org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:273) org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:241) org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:254) de.mycompany.mb.config.WebServiceConfigurationProvider.<init> (WebServiceConfigurationProvider.java:16) sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) java.lang.reflect.Constructor.newInstance(Constructor.java:513) java.lang.Class.newInstance0(Class.java:355) My logback.xml: <?xml version="1.0" encoding="UTF-8"?> <configuration> <contextName>${project.artifactId}</contextName> <property name="application-name" value="${project.artifactId}" /> <jmxConfigurator /> <appender name="DB" class="ch.qos.logback.classic.db.DBAppender"> <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>ERROR</level> </filter> <connectionSource class="ch.qos.logback.core.db.JNDIConnectionSource"> </connectionSource> </appender> <root> <level value="DEBUG" /> <appender-ref ref="DB" /> </root> </configuration> The Java code is very simple: public class LogbackTest { private final Logger logger = LoggerFactory.getLogger(LogbackTest.class); @PostConstruct public void init() throws IOException { logger.error("Test error message"); } } Is there probably a problem with my configuration or the way I use Logback? What can I do to avoid the connection leak error messages? I could simply disable connection leak detection, but I don't think that is the right way to deal with it. Thanks in advance for your help! Stephan -- View this message in context: http://old.nabble.com/Connection-leaks-with-DBAppender-and-GlassFish--tp321… Sent from the Logback User mailing list archive at Nabble.com.

2 2

SyslogAppender and TCP
by Daniel Serodio (lists) 05 Aug '11

05 Aug '11

Does logback's SyslogAppender work over TCP, or just UDP like log4j's ? Regards, Daniel Serodio

2 1

Why is Logback being configured twice?
by Daniel Serodio (lists) 04 Aug '11

04 Aug '11

I'm trying to switch an application from from log4j to Logback. This app uses SLF4J, Spring Framework and is deployed in Tomcat 7. Spring Framework uses JCL, so I added the following JARs to the application's classpath: slf4j-1.6.1.jar jcl-over-slf4j-1.6.1.jar logback-classic-0.9.29.jar logback-core-0.9.29.jar I created a logback.xml file, with debug="true" so I could debug my configuration. When I deploy this webapp in Tomcat, I can see that Logback is being configured twice. Why would this happen? Thanks in advance, Daniel Serodio

2 4