[logback-dev] [JIRA] Commented: (LBCORE-51) LoggerFactory doesnt respect custom ContextSelector
Ceki Gulcu (JIRA)
noreply-jira at qos.ch
Wed Aug 6 22:11:25 CEST 2008
[ http://jira.qos.ch/browse/LBCORE-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10631#action_10631 ]
Ceki Gulcu commented on LBCORE-51:
I apologize for the delay. I am afraid the fix for this bug requires changes to SLF4J's architecture. The kind of task not to be taken lightly.
Could you please describe your deployment scenario? Which web-server? In particular, where are the logback-* and slf4j-*.jar files located? Depending on the information you provide, I might have a solution....
> 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)
> My logger implementations
> 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"%>
> 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");
> 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