Thanks for pointing me in that direction.  I can see now that the jcl-over-slf4j LogFactory doesn&#39;t use the logging context selectors.<div><br></div><div>Ceki - is there a path forward from here for us?  Or are we just stuck with this behavior?  Could the jcl-over-slf4j LogFactory conceivably be changed to use context selectors?  Any other ideas/alternatives?<br>

<br><div class="gmail_quote">On Thu, Aug 16, 2012 at 4:04 PM, ceki <span dir="ltr">&lt;<a href="mailto:ceki@qos.ch" target="_blank">ceki@qos.ch</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<div class="im">On 16.08.2012 22:44, Robert Voliva wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Chris - by any chance are the messages that are ending up in the wrong<br>
context&#39;s log coming from commons-logging API loggers?  I seem to have<br>
narrowed down my issue to just statements logged through<br>
the jcl-over-slf4j dependency.  It seems like straight slf4j Logger<br>
statements are logging to the correct log files.<br>
</blockquote>
<br></div>
Both jcl-over-slf4j and log4j-over-slf4j cache the loggers they create. It follows that context selections does not work in the same way as they do for native slf4j, i.e. logback, loggers.<span class="HOEnZb"><font color="#888888"><br>


<br>
<br>
-- <br>
Ceki<br>
<a href="http://tinyurl.com/proLogback" target="_blank">http://tinyurl.com/proLogback</a></font></span><div class="HOEnZb"><div class="h5"><br>
______________________________<u></u>_________________<br>
Logback-user mailing list<br>
<a href="mailto:Logback-user@qos.ch" target="_blank">Logback-user@qos.ch</a><br>
<a href="http://mailman.qos.ch/mailman/listinfo/logback-user" target="_blank">http://mailman.qos.ch/mailman/<u></u>listinfo/logback-user</a><br>
</div></div></blockquote></div><br></div>