May 2013 - logback-user - mailman3.qos.ch

Fwd: Time based rolling on Android
by Jonas Schmid 13 May '13

13 May '13

Hi there, I am trying to use the time based rolling configuration for my android app. I got my configuration from the doc ( http://logback.qos.ch/manual/appenders.html#TimeBasedRollingPolicy) but it does not seem to work on my app. Please find enclosed my config file. The file does not roll and everything goes to log.log. To try it out I changed the date on my phone. I took care of killing the app before doing so. I also set the time to 23h59 then launched my app and waited, but it did not work either. What did I do wrong? Thanks Jonas

2 2

Release of logback version 1.0.13
by ceki 10 May '13

10 May '13

Hello all, I am happy to announce the release of logback version 1.0.13, a maintenance release containing only bug fixes and no new features. It should hit the Maven central repository by the time you read this message. Please refer to the news page for precise details of this release. http://logback.qos.ch/news.html You can receive logback related announcements by subscribing to the QOS.ch announce mailing list. To subscribe to QOS.ch announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/announce You may also receive announcements via twitter by following: https://twitter.com/qos_ch Enjoy, -- Ceki Gülcü

1 0

show the line number and method name when using logback with grails
by Meni Lubetkin 08 May '13

08 May '13

i'm using the logback plugin with grails 2.2.1 but it doesn't show the method or the class name. i defined the pattern using the logback reference but it not showing the line number or method name - it shows -1 all the time You could also reference http://markmail.org/message/**hfxw2w5auaqdea7i<http://markmail.org/message/hfxw2w5auaqdea7i> the plugin is now updated to 10.0.12 version

2 4

CONTEXT_NAME property with DBAppender
by Xavier Dury 08 May '13

08 May '13

Hi, I'm using a DBAppender and when I log something, I see that a LOG_EVENT_PROPERTY row with MAPPED_KEY = 'HOSTNAME' is inserted with the LOG_EVENT. Is there an option (in configuration) to make the CONTEXT_NAME visible too in the same way when using a ContextSelector or do I have to put it myself in the MDC through a Servlet Filter? Regards, Xavier

2 1

Multiple logback.xml, configuration merging/inheritance
by cowwoc 06 May '13

06 May '13

Hi, Is it possible to discuss http://jira.qos.ch/browse/LOGBACK-857 on this list? I'd like to get your feedback. I would send you a patch if I could, but I'm not sure how to implement the actual configuration merging process. Gili

3 2

default delimiter for MDC?
by Yoni Moses 06 May '13

06 May '13

Hi, I've been trying to use the new feature of the MDC without any luck.. it's probably a silly question, but can someone please post exact format for it? I've tried it without any luck... from what I've seen in the examples it seems like %X{req.xForwardedFor:-NONE} should work.. but for me it keeps on saying: ScanException: Expecting } under Parser.expectCurlyRight version is 1.0.12 with slf4j 1.7.5 Help is much appreciated ;) -- Cheers, Yoni

3 5

logback config scan doesn't detect changes in included files
by Richard Sand 05 May '13

05 May '13

Hi all – I’m wondering if this is expected behavior. I’ve a web application war file with a minimal logback.xml file in its WEB-INF/classes folder, which then uses a JNDI env variable to pull in a config file that is external to the application. This greatly facilitates deployment because I can override the env variable when I deploy the war (e.g. in Tomcat, a context.xml file) and specify the external location of the file, allowing me to deploy the war unchanged on different platforms and environments. But… I was hoping that having “scan=true” in the logback.xml file would allow me to alter the runtime logback configuration without restarting the context, but it doesn’t seem to be working. My logback.xml file: <configuration scan="true"> <insertFromJNDI env-entry-name="java:comp/env/appHome" as="appHome" /> <include file="${appHome}/conf/logback-app.xml"/> <contextListener class="ch.qos.logback.classic.jul.LevelChangePropagator"/> </configuration> Is this a bug or a known/accepted limitation of using scan=true? Thanks! Richard Sand | Managing Director PO Box 91824 | Austin | Texas 78709-1824 | USA Office: +1 888 612 8820 ext 02 | Fax: +1 866 304 3754 Mobile: +1 267 984 3651 [image: logo - small]

2 1

Trouble with setup logback to Oracle DB
by Horia Balog 03 May '13

03 May '13

Hi - need some help figuring out how to properly setup logback config to Oracle DB. I've managed to get it to work, but only getting the records in the DB when closing the logger. I am actually using logback through the Metrics library ( metrics.codahale.com) so using the logger through a metrics reporter object. But the end result is I can see the records (test records for now!) in the DB only at the end of the test when I stop the metrics reporter. Assuming this might be related to the config I'm using: <appender name="DatabaseAppender" class="ch.qos.logback.classic.db.DBAppender"> <connectionSource class="ch.qos.logback.core.db.DriverManagerConnectionSource"> <driverClass>oracle.jdbc.OracleDriver</driverClass> <url>jdbc:oracle:thin:@192.168.1.1:1521:XE</url> <user>abcde</user> <password>abcde</password> </connectionSource> </appender> Is there a way for me to change the config so each record inserted is committed right away? Thanks, Horia

1 0

DBAppender fails for find jndi dataSource from TomEE
by sgarlick 02 May '13

02 May '13

Hi, I've been having some issues setting up the DBAppender using a jndi DataSource supplied by TomEE. The datasource works fine in the application, but logback errors out when setting up its DBAppender with the same jndi location. Specifically JNDIConnectionSource.lookupDataSource throws a NamingException, which does the same lookup as my application code, but only the application code finds the datasource successfully. TomEE version 1.5.2 Logback classic 1.0.9 I've configured a DBAppender in logback.xml as so <appender name="DB" class="ch.qos.logback.classic.db.DBAppender"> <connectionSource class="ch.qos.logback.core.db.JNDIConnectionSource"> <jndiLocation>java:comp/env/jdbc/datasource</jndiLocation> </connectionSource> </appender> in web.xml <resource-ref> <res-ref-name>jdbc/datasource</res-ref-name> <res-type>javax.sql.DataSource</res-type> <res-auth>Container</res-auth> </resource-ref> in tomee context.xml <Resource name="jdbc/datasource" auth="Container" type="javax.sql.DataSource" factory="org.apache.tomcat.jdbc.pool.DataSourceFactory" maxActive="100" maxIdle="30" maxWait="10000" username="user" password="secret" driverClassName="oracle.jdbc.driver.OracleDriver" url="jdbc:oracle:thin:@(DESCRIPTION = (ADDRESS = (PROTOCOL = TCP) (HOST = localhost)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED)(SERVICE_NAME = SERVICE)))" /> and my application dataSource bean successfully finds the dataSource Context ctx = new InitialContext(); return (DataSource) ctx.lookup("java:comp/env/jdbc/datasource"); Please let me know if anymore information is needed. -- View this message in context: http://logback.10977.n7.nabble.com/DBAppender-fails-for-find-jndi-dataSourc… Sent from the Users mailing list archive at Nabble.com.

2 5

SocketAppender question
by Will Mason 01 May '13

01 May '13

Hello, I had a question about the design of SocketAppender. Why does the appender spawn a thread to try to connect to an unconnected socket? Could someone please explain how that is better than just trying to reconnect when a log event reaches an unconnected appender? Thanks for any information, Will

2 2