[logback-dev] [JIRA] Updated: (LBCLASSIC-39) no log messages after redeployment

[Ceki Gulcu (JIRA)]

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

Ceki Gulcu updated LBCLASSIC-39:
--------------------------------

    Attachment: jedi0.zip

I have attached a test web-application. I have tested it with logback
version 0.9.13. I can start and stop application without problems. I
get the following output in catalina.out (see below).

Consequently, I cannot reproduce the problem you describe. Several
LoggerContext bugs were corrected in logback recently which explain
the descrepancy.  You please see if the problem you observed has been
corrected in recent versions of logback? As a side note, you really
should use SLF4J version 1.5.6 which solves a LoggerContext related
issue.

INFO: D�marrage de Coyote HTTP/1.1 sur http-9090
5 déc. 2008 19:39:06 org.apache.catalina.startup.Catalina start
INFO: Server startup in 455 ms
JEDI0 2008-12-05 19:39:10,828 DEBUG -in doGet()
19:39:10,734 |-INFO in ch.qos.logback.classic.selector.ContextJNDISelector at e61fd1 - Searching for [logback-jedi0.xml]
19:39:10,765 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not set
19:39:10,765 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender]
19:39:10,765 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [CON]
19:39:10,781 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Popping appender named [CON] from the object stack
19:39:10,781 |-INFO in ch.qos.logback.classic.joran.action.JMXConfiguratorAction - begin
19:39:10,828 |-INFO in ch.qos.logback.classic.joran.action.LevelAction - root level set to DEBUG
19:39:10,828 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [CON] to Logger[root]

About to detach context named jedi0
JEDI0 2008-12-05 19:39:26,531 WARN  -Stopping logger context jedi0
JEDI0 2008-12-05 19:39:57,875 DEBUG -in doGet()
19:39:57,859 |-INFO in ch.qos.logback.classic.selector.ContextJNDISelector at e61fd1 - Searching for [logback-jedi0.xml]
19:39:57,875 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not set
19:39:57,875 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender]
19:39:57,875 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [CON]
19:39:57,875 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Popping appender named [CON] from the object stack
19:39:57,875 |-INFO in ch.qos.logback.classic.joran.action.JMXConfiguratorAction - begin
19:39:57,875 |-INFO in ch.qos.logback.classic.joran.action.LevelAction - root level set to DEBUG
19:39:57,875 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [CON] to Logger[root]


> no log messages after redeployment
> ----------------------------------
>
>                 Key: LBCLASSIC-39
>                 URL: http://jira.qos.ch/browse/LBCLASSIC-39
>             Project: logback-classic
>          Issue Type: Bug
>          Components: Other
>    Affects Versions: unspecified
>         Environment: Operating System: Windows
> Platform: PC
>            Reporter: Ingo Siebert
>            Assignee: Logback dev list
>            Priority: Blocker
>             Fix For: 0.9.13
>
>         Attachments: jedi0.zip
>
>
> Hi,
> I use the JNDI switch for logback.
> If I undeploy my application, the old JNDI context ist destroyed (it's a log messge). That's fine.
> But I redeploy the same application with the same context name, no logging messages are displayed. That's very frustrating.
> If I restart Tomcat6, then the deployed application comes up and i see the messages again.
> The libs which are needed by my application are stored in the tomcat6/sharedLib folder.
> Any idea why the messages are missing?
> Ingo
> This is my web.xml:
> <filter>
> <filter-name>LoggerContextFilter</filter-name>
> <filter-class>ch.qos.logback.classic.selector.servlet.LoggerContextFilter</filter-class>
> </filter>
> <filter-mapping>
>   <filter-name>LoggerContextFilter</filter-name>
>   <url-pattern>/*</url-pattern>
> </filter-mapping>
> <listener> <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
> </listener>
> <!-- Detaches logger repositories. -->
> <listener>
> <listener-class>ch.qos.logback.classic.selector.servlet.ContextDetachingSCL</listener-class>
> </listener>
> ...
> <env-entry>
>   <description>JNDI logging context for this app</description>
>   <env-entry-name>logback/context-name</env-entry-name>
>   <env-entry-value>EIMContext-1</env-entry-value>
>   <env-entry-type>java.lang.String</env-entry-type>
> </env-entry>
> <env-entry>
>   <description>URL for configuring logback context</description>
>   <env-entry-name>logback/configuration-resource</env-entry-name>
>   <env-entry-value>eim_logback.xml</env-entry-value>
>   <env-entry-type>java.lang.String</env-entry-type>
> </env-entry>

-- 
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