headers
Grzegorz Grzybek (JIRA | 2 Nov 2010 08:38
Picon

[JIRA] Created: (LBACCESS-17) LogbackValve overrides final start() method from LifecycleBase in Tomcat 7

LogbackValve overrides final start() method from LifecycleBase in Tomcat 7
--------------------------------------------------------------------------

                 Key: LBACCESS-17
                 URL: http://jira.qos.ch/browse/LBACCESS-17
             Project: logback-access
          Issue Type: Bug
    Affects Versions: 0.9.26
            Reporter: Grzegorz Grzybek
            Assignee: Logback dev list
            Priority: Critical

{code}
java.lang.VerifyError: class ch.qos.logback.access.tomcat.LogbackValve overrides final method start.()V
{code}
Tomcat 7 has changed the LifecycleBase implementation - it should not override start() but rather startInternal()

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Permalink | Reply | 3 comments |
headers
Simon Kelly (JIRA | 3 Nov 2010 11:30
Picon

[JIRA] Created: (LBCLASSIC-227) HOSTNAME property not resolved

HOSTNAME property not resolved
------------------------------

                 Key: LBCLASSIC-227
                 URL: http://jira.qos.ch/browse/LBCLASSIC-227
             Project: logback-classic
          Issue Type: Bug
    Affects Versions: 0.9.26
            Reporter: Simon Kelly
            Assignee: Logback dev list

When using the hostname property the following ERROR message is logged:

	Appender [EMAIL] of type [ch.qos.logback.classic.net.SMTPAppender] has no appplicable [HOSTNAME]
property 

Configuration as below:
=======================================================
import ch.qos.logback.classic.encoder.PatternLayoutEncoder 
import ch.qos.logback.core.ConsoleAppender
import ch.qos.logback.classic.net.SMTPAppender
import ch.qos.logback.core.status.OnConsoleStatusListener
import ch.qos.logback.classic.PatternLayout
import ch.qos.logback.classic.html.HTMLLayout

import static ch.qos.logback.classic.Level.TRACE
import static ch.qos.logback.classic.Level.DEBUG
import static ch.qos.logback.classic.Level.INFO
import static ch.qos.logback.classic.Level.WARN
import static ch.qos.logback.classic.Level.ERROR
(Continue reading)

Permalink | Reply | 4 comments |
headers
Simon Kelly (JIRA | 3 Nov 2010 11:34
Picon

[JIRA] Created: (LBCLASSIC-228) Revert to previous configuration if configuration fails during scan

Revert to previous configuration if configuration fails during scan
-------------------------------------------------------------------

                 Key: LBCLASSIC-228
                 URL: http://jira.qos.ch/browse/LBCLASSIC-228
             Project: logback-classic
          Issue Type: Improvement
    Affects Versions: 0.9.26
            Reporter: Simon Kelly
            Assignee: Logback dev list

With logback configured to scan for changes in the config file, if the change causes an error in the
configuration (e.g. syntax of undefined property) the logger remains unconfigured and does not perform
any future scans. The only way to reconfigure the logger is to restart the applicaiton (in the case of a webapp).

It would be good for logback to be able to recover from such an error by reverting to the previous
configuration so that logging continues and also the error in the config file may be fixed.

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Permalink | Reply | 4 comments |
headers
Simon Kelly (JIRA | 3 Nov 2010 11:38
Picon

[JIRA] Commented: (LBCLASSIC-227) HOSTNAME property not resolved


    [
http://jira.qos.ch/browse/LBCLASSIC-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11877#action_11877
] 

Simon Kelly commented on LBCLASSIC-227:
---------------------------------------

The property is also not resolved if used in a def statement:

def hostname = "${HOSTNAME}"

Stack trace:
===========================
Exception in thread "Thread-19" groovy.lang.MissingPropertyException: No such property: HOSTNAME
for class: Script1
        at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:49)
        at org.codehaus.groovy.runtime.callsite.PogoGetPropertySite.getProperty(PogoGetPropertySite.java:49)
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGroovyObjectGetProperty(AbstractCallSite.java:239)
        at Script1.run(Script1.groovy:18)
        at Script1$run.call(Unknown Source)
        at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:40)
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116)
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:120)
        at ch.qos.logback.classic.gaffer.GafferConfigurator.run(GafferConfigurator.groovy:58)
        at ch.qos.logback.classic.gaffer.GafferConfigurator$run$0.callCurrent(Unknown Source)
        at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:44)
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:141)
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:149)
        at ch.qos.logback.classic.gaffer.GafferConfigurator.run(GafferConfigurator.groovy:41)
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ceki Gulcu (JIRA | 3 Nov 2010 13:44
Picon

[JIRA] Assigned: (LBCLASSIC-227) HOSTNAME property not resolved


     [
http://jira.qos.ch/browse/LBCLASSIC-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ceki Gulcu reassigned LBCLASSIC-227:
------------------------------------

    Assignee: Ceki Gulcu  (was: Logback dev list)

> HOSTNAME property not resolved
> ------------------------------
>
>                 Key: LBCLASSIC-227
>                 URL: http://jira.qos.ch/browse/LBCLASSIC-227
>             Project: logback-classic
>          Issue Type: Bug
>    Affects Versions: 0.9.26
>            Reporter: Simon Kelly
>            Assignee: Ceki Gulcu
>
> When using the hostname property the following ERROR message is logged:
> 	Appender [EMAIL] of type [ch.qos.logback.classic.net.SMTPAppender] has no appplicable [HOSTNAME]
property 
> Configuration as below:
> =======================================================
> import ch.qos.logback.classic.encoder.PatternLayoutEncoder 
> import ch.qos.logback.core.ConsoleAppender
> import ch.qos.logback.classic.net.SMTPAppender
> import ch.qos.logback.core.status.OnConsoleStatusListener
> import ch.qos.logback.classic.PatternLayout
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ceki Gulcu (JIRA | 3 Nov 2010 13:46
Picon

[JIRA] Assigned: (LBCLASSIC-228) Revert to previous configuration if configuration fails during scan


     [
http://jira.qos.ch/browse/LBCLASSIC-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ceki Gulcu reassigned LBCLASSIC-228:
------------------------------------

    Assignee: Ceki Gulcu  (was: Logback dev list)

> Revert to previous configuration if configuration fails during scan
> -------------------------------------------------------------------
>
>                 Key: LBCLASSIC-228
>                 URL: http://jira.qos.ch/browse/LBCLASSIC-228
>             Project: logback-classic
>          Issue Type: Improvement
>    Affects Versions: 0.9.26
>            Reporter: Simon Kelly
>            Assignee: Ceki Gulcu
>
> With logback configured to scan for changes in the config file, if the change causes an error in the
configuration (e.g. syntax of undefined property) the logger remains unconfigured and does not perform
any future scans. The only way to reconfigure the logger is to restart the applicaiton (in the case of a webapp).
> It would be good for logback to be able to recover from such an error by reverting to the previous
configuration so that logging continues and also the error in the config file may be fixed.

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ceki Gulcu (JIRA | 3 Nov 2010 13:46
Picon

[JIRA] Updated: (LBCLASSIC-228) Revert to previous configuration if configuration fails during scan


     [
http://jira.qos.ch/browse/LBCLASSIC-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ceki Gulcu updated LBCLASSIC-228:
---------------------------------

    Priority: Critical  (was: Major)

> Revert to previous configuration if configuration fails during scan
> -------------------------------------------------------------------
>
>                 Key: LBCLASSIC-228
>                 URL: http://jira.qos.ch/browse/LBCLASSIC-228
>             Project: logback-classic
>          Issue Type: Improvement
>    Affects Versions: 0.9.26
>            Reporter: Simon Kelly
>            Assignee: Ceki Gulcu
>            Priority: Critical
>
> With logback configured to scan for changes in the config file, if the change causes an error in the
configuration (e.g. syntax of undefined property) the logger remains unconfigured and does not perform
any future scans. The only way to reconfigure the logger is to restart the applicaiton (in the case of a webapp).
> It would be good for logback to be able to recover from such an error by reverting to the previous
configuration so that logging continues and also the error in the config file may be fixed.

--

-- 
This message is automatically generated by JIRA.
-
(Continue reading)

Permalink | Reply | 0 comments |
headers
added by portage for gitosis-gentoo | 3 Nov 2010 18:02
Picon

[GIT] Logback: the generic, reliable, fast and flexible logging framework. branch, master, updated. v_0.9.25-17-g1869d32

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Logback: the generic, reliable, fast and flexible logging framework.".

The branch, master has been updated
       via  1869d32c56f08e2a1af168ddf82219a37f05f633 (commit)
      from  5e51ada8f7bb344d6e16f3e0a5678353dc413ec4 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
http://git.qos.ch/gitweb/?p=logback.git;a=commit;h=1869d32c56f08e2a1af168ddf82219a37f05f633
http://github.com/ceki/logback/commit/1869d32c56f08e2a1af168ddf82219a37f05f633

commit 1869d32c56f08e2a1af168ddf82219a37f05f633
Author: Ceki Gulcu <ceki@...>
Date:   Wed Nov 3 18:00:59 2010 +0100

    adding recipes

diff --git a/logback-site/src/site/pages/manual/migrationFromLog4j.html b/logback-site/src/site/pages/manual/migrationFromLog4j.html
index 5d5fe00..6f44908 100644
--- a/logback-site/src/site/pages/manual/migrationFromLog4j.html
+++ b/logback-site/src/site/pages/manual/migrationFromLog4j.html
 <at>  <at>  -138,9 +138,9  <at>  <at>  public class TrivialLogbackLayout extends <b>LayoutBase&lt;ILoggingEvent></b> {

    <h3>Migrating a log4j appender</h3>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Joern Huxhorn (JIRA | 3 Nov 2010 21:10
Picon

[JIRA] Created: (LBCLASSIC-229) One test fails in latest commit 1869d32c56f08e2a1af1

One test fails in latest commit 1869d32c56f08e2a1af1
----------------------------------------------------

                 Key: LBCLASSIC-229
                 URL: http://jira.qos.ch/browse/LBCLASSIC-229
             Project: logback-classic
          Issue Type: Bug
          Components: Other
    Affects Versions: 0.9.26
         Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
Java version: 1.6.0_20
Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home
Default locale: en_US, platform encoding: MacRoman
OS name: "mac os x" version: "10.6.4" arch: "x86_64" Family: "mac"
            Reporter: Joern Huxhorn
            Assignee: Logback dev list
            Priority: Minor

Unfortunately, one of the two fails of LBCLASSIC-223 just showed up again.

You haven't changed anything related in the commit in question so this is definitely a timing issue and
isn't showing up all the time.

Error Message

effective=3, expected=4

Stacktrace

java.lang.AssertionError: effective=3, expected=4
(Continue reading)

Permalink | Reply | 0 comments |
headers
Michael Osipov (JIRA | 4 Nov 2010 15:18
Picon

[JIRA] Created: (LBCLASSIC-230) %cn conversion word fails in SMTPAppender subject

%cn conversion word fails in SMTPAppender subject
-------------------------------------------------

                 Key: LBCLASSIC-230
                 URL: http://jira.qos.ch/browse/LBCLASSIC-230
             Project: logback-classic
          Issue Type: Bug
          Components: layout
    Affects Versions: 0.9.26
            Reporter: Michael Osipov
            Assignee: Logback dev list

According to the docs, the subject pattern equals to the pattern layout. Putting a %cn into it fails with an exception

{noformat}
<Subject>${HOSTNAME} %cn %level %X{ad.displayName} %logger{20} - %.20msg - %ex{-1}</Subject>
{noformat}

{noformat}
15:13:56,973 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate
appender of type [ch.qos.logback.classic.net.SMTPAppender]
15:13:57,045 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [EMAIL]
15:13:57,525 |-ERROR in ch.qos.logback.core.pattern.parser.Compiler <at> 1a54421 - Failed to
instantiate converter class [ch.qos.logback.classic.joran.action.ContextNameAction] ch.qos.logback.core.util.IncompatibleClassException
        at ch.qos.logback.core.util.IncompatibleClassException
        at      at ch.qos.logback.core.util.OptionHelper.instantiateByClassName(OptionHelper.java:47)
        at      at ch.qos.logback.core.util.OptionHelper.instantiateByClassName(OptionHelper.java:31)
        at      at ch.qos.logback.core.pattern.parser.Compiler.createConverter(Compiler.java:101)
        at      at ch.qos.logback.core.pattern.parser.Compiler.compile(Compiler.java:58)
        at      at ch.qos.logback.core.pattern.parser.Parser.compile(Parser.java:66)
(Continue reading)

Permalink | Reply | 1 comment |

Gmane