Paul, I have very briefly looked at your code. Here are some hopefully relevant comments. First, why aren't you using JNDIContextSelector? Second, you indicate that you have created your own ContextSelector, but have you registered it with a logback's implementation of StaticLoggerBinder? You would do that by setting the system property "logback.ContextSelector" to "org.red5.logging.LoggingContextSelector". OK, I see that your docs actually refer to "logback.ContextSelector" system property. Is an instnace of org.red5.logging.LoggingContextSelector being instantiated at all? Looking at the dynamicalContextSelector method in logback's implementation of StaticLoggerBinder, the cons.newInstance(defaultLoggerContext) call does not look right. It should probably be cons.newInstance(new Object[] {defaultLoggerContext}) Is it possible for you to compile logback and check whether my suspicion is correct? I don't have the possibility to check this right now. My apologies. HTH, Paul Gregoire (JIRA) wrote:
[ http://jira.qos.ch/browse/LBCORE-24?page=com.atlassian.jira.plugin.system.is... ]
Paul Gregoire commented on LBCORE-24: -------------------------------------
First off I must say that I've grown very disenchanted with all the logging frameworks out there. Problems like this just plain frustrating, there is way too much "magic" happening behind our backs. But to get on with my comment.. I have tried for several days to get slf4j and logback to work in harmony with Red5. Everything works well until you try to separate logging into web contexts or red5 app instances, all logging continues to go the topmost default level. I have created a log context selector, log filter, and log listener but they dont work properly.. maybe you guys can see where i've gone wrong? http://svn1.cvsdude.com/osflash/red5/java/server/trunk/src/org/red5/logging/ I have also tried to use the non-static non-final logging patter in my red5 apps but it doesnt improve anything.