Josh Chappelle (JIRA | 31 Oct 21:01 2014
Picon

[JIRA] (LOGBACK-932) Modifying DynamicThresholdFilter (TurboFilter) programatically at runtime

I am needing this because I would like to build a user interface for setting the log level for a specific user at runtime. I can create the filter dynamically but I can't update or remove the MDCValueLevelPair afterwards.

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
Darius X. (JIRA | 27 Oct 18:52 2014
Picon

[JIRA] (LOGBACK-204) file appender that rolls on startup

Change By: Darius X. (27/Oct/14 6:51 PM)
Comment: Since the file-rename during rollover occasionally fails on Windows, it would be nice to be able to do the check on start-up (not just rollover unconditionally on start-up)
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
Robin Stocker (JIRA | 27 Oct 07:34 2014
Picon

[JIRA] (LOGBACK-775) Smart search for exception cause

Robin Stocker commented on LOGBACK-775

We have a subclass of ThrowableProxyConverter here, where we used to override throwableProxyToString to add this. Since 1.1.0, it got a bit harder to do this because some package-protected methods were changed.

If I were to contribute this, what solution would the Logback developers like to see?

SQLException in ThrowableProxyConverter.recursiveAppend could be another special case (like suppressed exceptions).

Or there could be a new protected Iterable<IThrowableProxy> getAdditionalExceptions(IThrowableProxy tp), where subclasses could add any additional exceptions they want. Any returned values would be handled using recursiveAppend (with a different prefix).

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
Hamid Asaadi (JIRA | 25 Oct 14:12 2014
Picon

[JIRA] (LOGBACK-1026) Custom Appenders cause error and fail to load in Play! Framework

Hamid Asaadi commented on LOGBACK-1026
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
Hamid Asaadi (JIRA | 25 Oct 14:10 2014
Picon

[JIRA] (LOGBACK-1026) Custom Appenders cause error and fail to load in Play! Framework

Issue Type: Bug
Assignee: Logback dev list
Created: 25/Oct/14 2:09 PM
Description:

A custom Appender class inside the project fails to load on application start with this trace:
12:57:41,858 |-ERROR in ch.qos.logback.core.joran.action.AppenderAction - Could not create an Appender of type [util.logger.XXX]. ch.qos.logback.core.util.DynamicClassLoadingException: Failed to instantiate type util.logger.XXX
....
Caused by: java.lang.ClassNotFoundException: util.logger.XXX
at at java.net.URLClassLoader$1.run(URLClassLoader.java:372)
at at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at at java.security.AccessController.doPrivileged(Native Method)
at at java.net.URLClassLoader.findClass(URLClassLoader.java:360)
at at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at at ch.qos.logback.core.util.OptionHelper.instantiateByClassNameAndParameter(OptionHelper.java:60)

This thread on StackOverflow is also referring to the same problem with a couple of workarounds, but actually none is really a solution.

Project: logback
Priority: Major
Reporter: Hamid Asaadi
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
Jason Klapste (JIRA | 24 Oct 16:49 2014
Picon

[JIRA] (LOGBACK-988) logback does not always close log files

Jason Klapste commented on LOGBACK-988

entry.timestamp looks to refer to the last time it was used-- which of course a logging event would force an update. The SiftingAppender documentation states:

Whenever SiftingAppender sees a logging event marked as FINALIZE_SESSION it will end-of-life the associated nested appender. Upon reaching its end-of-life, a nested appender will linger for a few seconds to process any late coming events (if any) and then will be closed.

With the current implementation any additional logging events would extend that linger window for 10 seconds from the last event. This would seem like a reasonable implementation as forcing a close just because the 10 seconds expired even if we're continuing to receive logging events for that appender would very likely cause us to immediately open the file back up.

Your adminlog isn't being closed due to LOGBACK-940.

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
Darius X. (JIRA | 22 Oct 17:46 2014
Picon

[JIRA] (LOGBACK-204) file appender that rolls on startup

Darius X. commented on LOGBACK-204

Since the file-rename during rollover occasionally fails on Windows, it would be nice to be able to do the check on start-up (not just rollover unconditionally on start-up)

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
Martin Goldhahn (JIRA | 22 Oct 13:48 2014
Picon

[JIRA] (LOGBACK-1025) Please reintroduce the GSiftingAppender

Issue Type: Bug
Assignee: Logback dev list
Created: 22/Oct/14 1:47 PM
Description:

We have to stick with version 1.0.11 of logback because the GSiftingAppender was removed in 1.0.12. Please reintroduce this feature.

Project: logback
Priority: Major
Reporter: Martin Goldhahn
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
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

Gmane