log4j doesn't clean up olf values in the MDC. It is up to you to clean up the old values. i.e. If you are in a servlet container than reset all MDC values at the beginning of each request (just to be sure) and clear them at the end of the request (to allow GC).
On 9/4/06, Meera Mehta <[EMAIL PROTECTED]> wrote:
Hi, Log4J provides the MDC to set the variables in ThreadLocal. How Log4J manages the thread clean up when the thread is returned to the pool. In case of improper thread clean up, there may be chances that old values will be available, when the same thread is reused. Could you please throw some light on ThreadLocal (MDC) management in Log4J. Thanks and Regards, __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- James Stauffer http://www.geocities.com/stauffer_james/ Are you good? Take the test at http://www.livingwaters.com/good/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]