[logback-dev] [JIRA] Commented: (LBCORE-51) LoggerFactory doesnt respect custom ContextSelector

Paul Gregoire (JIRA) noreply-jira at qos.ch
Fri Aug 8 02:28:25 CEST 2008

    [ http://jira.qos.ch/browse/LBCORE-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10635#action_10635 ] 

Paul Gregoire commented on LBCORE-51:

The zip file i posted the link for contains the exact layout that we use for Red5 (currently in version 0.7.1-dev). Our default setup in trunk uses Tomcat 6.0.16 embedded within Red5 which is configured via Spring 2.5.5; Jetty is also available but is no longer the default. I normally place all the log jars in the main "common" lib directory /red5/lib/ and our primary logback config is placed here /red5/conf/logback.xml. The red5 applications are essentially webapps with extra spring configs and they exist in a structure exactly modeled after Tomcat and Jetty; they are placed within /red5/webapps/. Each webapp contains its own log config: /red5/webapps/myapp/WEB-INF/classes/logback.xml I have also tried using form logback-myapp.xml.
A solution that we would like to see would provide all the logs designated in the /red5/conf/logback.xml created separately from any log created by an individual webapp. This seems to be simple to implement but in practice turns out to be difficult for those of us that don't have your intimate knowledge regarding the log systems.

> LoggerFactory doesnt respect custom ContextSelector
> ---------------------------------------------------
>                 Key: LBCORE-51
>                 URL: http://jira.qos.ch/browse/LBCORE-51
>             Project: logback-core
>          Issue Type: Bug
>         Environment: Windows XP64, Java 6, Red5 v0.7.1-dev, Logback 0.9.9, Slf4j 1.5.0
>            Reporter: Paul Gregoire
>            Assignee: Logback dev list
> I have found that calling LoggerFactory.getLogger(xxxx) does not make calls to my custom context selector. I expect to see a call to getLoggerContext() but I dont. Do I need to create my own LoggerFactory impl to get my web context apps and red5 apps to use their own Loggers?
> Main Red5 trunk (dev)
> http://svn1.cvsdude.com/osflash/red5/java/server/trunk/
> My logger implementations
> http://svn1.cvsdude.com/osflash/red5/java/server/trunk/src/org/red5/logging/
> Example JSP I used to test the log context selection
> <%@page import="org.slf4j.Logger,org.slf4j.LoggerFactory,org.slf4j.impl.StaticLoggerBinder,ch.qos.logback.classic.LoggerContext,org.red5.logging.LoggingContextSelector"%>
> <html>
> <body>
> <%
> //
> Logger log = LoggerFactory.getLogger("TestJsp");
> log.info("This is a test log entry from a web context");
> //
> LoggingContextSelector selector = (LoggingContextSelector) StaticLoggerBinder.SINGLETON.getContextSelector();		
> LoggerContext ctx = selector.getLoggerContext(mywebappcontextname);
> Logger log2 = ctx.getLogger("TestJsp");
> log2.info("This is a test log entry from a web context attempt 2");
> %>
> </body>
> </html>
> The first log goes to the "default" logger context and the second goes to the correct one. I also implemented the Servlet filter and context listener for this tested context.
> Anything I can do to help, please let me know.. I am getting extremely frustrated with this logging stuff and I'm sure our users are as well.

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


More information about the logback-dev mailing list