Adrian Fortuzi (JIRA | 20 Oct 15:56 2014
Picon

[JIRA] (LOGBACK-941) The MDC properties are not set to LoggingEvent when logging over the SocketAppender

This issue is related to http://jira.qos.ch/browse/LOGBACK-905,
Seems to be the same problem.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
logback-dev mailing list
logback-dev@...
http://mailman.qos.ch/mailman/listinfo/logback-dev
Carlos Ferreira (JIRA | 16 Oct 17:18 2014
Picon

[JIRA] (LOGBACK-1024) Performance issue on AIX

Issue Type: Bug
Assignee: Logback dev list
Created: 16/Oct/14 5:16 PM
Description:

We have an application running on WebSphere and AIX that was using logback 0.9.29 and noticed that after upgrading to the latest version (1.1.2) the execution time increased 34.18%. This time was obtained after running some transactions where the only change was the logback version. For this reason, we had to downgrade the version.

Project: logback
Priority: Major
Reporter: Carlos Ferreira
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
logback-dev mailing list
logback-dev@...
http://mailman.qos.ch/mailman/listinfo/logback-dev
Matthew Edge (JIRA | 14 Oct 04:34 2014
Picon

[JIRA] (LOGBACK-957) Add Groovy support for SiftingAppender

Matthew Edge commented on LOGBACK-957

I would like to bump this issue. We are in the process of removing XML-based configurations from our project in favor of Groovy and YAML configs, and the SiftingFileAppender is a must have for our project.

A recommendation for an "in the meantime" fix would also be great

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
logback-dev mailing list
logback-dev@...
http://mailman.qos.ch/mailman/listinfo/logback-dev
Jelmer Kuperus (JIRA | 10 Oct 14:04 2014
Picon

[JIRA] (LOGBACK-1023) Tee filter ignores response character encoding when

Issue Type: Bug
Affects Versions: 1.1.1
Assignee: Logback dev list
Components: logback-access
Created: 10/Oct/14 2:03 PM
Description:

When configuring the Tee filter we ran into an issue where the wrong character encoding is used when writing to the response. The fix is to simply use the correct character encoding when constructing the printwriter in the ResponseWrapper

Pull request that fixes the issue :https://github.com/qos-ch/logback/pull/224

Project: logback
Priority: Major
Reporter: Jelmer Kuperus
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
logback-dev mailing list
logback-dev@...
http://mailman.qos.ch/mailman/listinfo/logback-dev
Paul Krause (JIRA | 7 Oct 22:55 2014
Picon

[JIRA] (LOGBACK-1022) Make DBAppender work with unreliable database connection

Issue Type: Bug
Affects Versions: 1.1.2
Assignee: Logback dev list
Components: logback-classic
Created: 07/Oct/14 10:55 PM
Description:

We have configured DBAppender to log to a SQL Server database from a Spring webapp under Tomcat using ch.qos.logback.core.db.DataSourceConnectionSource. This works fine, except that when the host reboots (this is Windows, after all), Tomcat restarts faster than SQL Server does, so when DataSourceConnectionSource is first started, it fails to connect to the database.

There should be a way to detect this and retry the connection., Alternately, there should be a way for the application to check DBAppender's state and tell it to reconnect if needed.

12:11:11,593 |-WARN in ch.qos.logback.core.db.DataSourceConnectionSource <at> 134c00a9 - Could not discover the dialect to use. java.sql.SQLException: Cannot open database requested by the login. The login failed.
at java.sql.SQLException: Cannot open database requested by the login. The login failed.
at at ch.qos.logback.core.db.DataSourceConnectionSource.getConnection(DataSourceConnectionSource.java:63)
at at ch.qos.logback.core.db.ConnectionSourceBase.discoverConnectionProperties(ConnectionSourceBase.java:48)
at at ch.qos.logback.core.db.DataSourceConnectionSource.start(DataSourceConnectionSource.java:44)
at at ch.qos.logback.core.joran.action.NestedComplexPropertyIA.end(NestedComplexPropertyIA.java:167)
at at ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:317)
at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:196)
at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:182)
at at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:62)
at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:149)
at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:135)
at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:99)
at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:49)
at at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:75)
at at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:150)
at at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:85)
at at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:55)
at at org.slf4j.LoggerFactory.bind(LoggerFactory.java:129)
at at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:108)
at at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:302)
at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:276)
at at org.apache.commons.logging.impl.SLF4JLogFactory.getInstance(SLF4JLogFactory.java:156)
at at org.apache.commons.logging.impl.SLF4JLogFactory.getInstance(SLF4JLogFactory.java:132)
at at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:274)
at at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:282)

Environment:

logback 1.1.2 with slf4j 1.7.7, using DBAppender to log to a SQL Server database from a Spring webapp under Tomcat via ch.qos.logback.core.db.DataSourceConnectionSource

Project: logback
Labels: dbappender
Priority: Major
Reporter: Paul Krause
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
logback-dev mailing list
logback-dev@...
http://mailman.qos.ch/mailman/listinfo/logback-dev
Fadi Mohsen (JIRA | 3 Oct 14:04 2014
Picon

[JIRA] (LOGBACK-1019) SyslogAppender leaks file descriptors

Issue Type: Bug
Affects Versions: 1.1.2
Assignee: Logback dev list
Components: logback-core
Created: 03/Oct/14 2:02 PM
Description:

When reinitiating/reinitializing logback, one is supposted to call detachAndStopAllAppenders, that method in turn will end up calling close on all SyslogAppender's , but the implementation in SyslogAppender does not actually close the DatagramSocket by calling the close method, but leave it to GC to collect by killing references.

We refresh application configuration each 10 seconds ( reinitating the logging as well ) that makes all applications leak UDP sockets (filedsc).

Log4j fixed this in 1.2.17.

Environment:

Linux

Project: logback
Priority: Blocker
Reporter: Fadi Mohsen
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
logback-dev mailing list
logback-dev@...
http://mailman.qos.ch/mailman/listinfo/logback-dev
Picon

[JIRA] (LOGBACK-638) Add ability to manually specify configuration BEFORE autoconfiguration

The ability to have custom initialization hook would be still very useful. In my environment, I have two JEE applications deployed onto a single JBoss instance. I have to differentiate logging config for each. Now, I'm bundling logback.xml in application, but I would have to load the configuration from external file (i.e. different for PROD and DEV environment). I can not use any global system property, since it would affect both applications. Perfectly, I would use the mentioned above logback.configurationClass property, to specify my code, which would implement required logic.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
logback-dev mailing list
logback-dev@...
http://mailman.qos.ch/mailman/listinfo/logback-dev
Gili (JIRA | 29 Sep 07:29 2014
Picon

[JIRA] (LOGBACK-1018) WriterAppender Javadoc refers to nonexistent documentation/link

Gili commented on LOGBACK-1018

Upon further investigation, it looks like the file in question should not exist (WriterAppender was renamed to OutputStreamAppender). The Javadoc file should probably be deleted from the website.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
logback-dev mailing list
logback-dev@...
http://mailman.qos.ch/mailman/listinfo/logback-dev
Gili (JIRA | 29 Sep 07:29 2014
Picon

[JIRA] (LOGBACK-1017) Typo in WriterAppender Javadoc

Gili commented on LOGBACK-1017

Upon further investigation, it looks like the file in question should not exist (WriterAppender was renamed to OutputStreamAppender). The Javadoc file should probably be deleted from the website.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
logback-dev mailing list
logback-dev@...
http://mailman.qos.ch/mailman/listinfo/logback-dev
Gili (JIRA | 29 Sep 04:54 2014
Picon

[JIRA] (LOGBACK-1018) WriterAppender Javadoc refers to nonexistent documentation/link

Gili created LOGBACK-1018
Issue Type: Bug
Affects Versions: 1.1.2
Assignee: Logback dev list
Components: logback-core
Created: 29/Sep/14 4:52 AM
Description:

http://logback.qos.ch/apidocs/ch/qos/logback/core/WriterAppender.html reads:

please refer to the online manual at http://logback.qos.ch/manual/appenders.html#WriterAppender

but there is no such anchor and the page does not mention WriterAppender at all.

Project: logback
Priority: Trivial
Reporter: Gili
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
logback-dev mailing list
logback-dev@...
http://mailman.qos.ch/mailman/listinfo/logback-dev
Gili (JIRA | 29 Sep 04:52 2014
Picon

[JIRA] (LOGBACK-1017) Typo in WriterAppender Javadoc

Gili created LOGBACK-1017
Issue Type: Bug
Affects Versions: 1.1.2
Assignee: Logback dev list
Components: logback-core
Created: 29/Sep/14 4:51 AM
Description:

http://logback.qos.ch/apidocs/ch/qos/logback/core/WriterAppender.html reads:

WriterAppender appends events to a hava.io.Writer

The last word should be "java.io.Writer".

Project: logback
Priority: Trivial
Reporter: Gili
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
logback-dev mailing list
logback-dev@...
http://mailman.qos.ch/mailman/listinfo/logback-dev

Gmane