[logback-dev] [JIRA] Resolved: (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 resolved LBCLASSIC-39.
---------------------------------

    Fix Version/s: 0.9.13
       Resolution: Cannot Reproduce

I am marking this issue as CANNOT REPRODUCE. Please re-open it if it has not been corrected in 0.9.13.

> 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