Well, actually that doesn't work in either my local build or the webstart-deployed build.
I fear something else may be at fault... I'm not seeing anything in the MDC column at all now. We are using a 1.2.8 SocketAppender to send events that are laid out by a branched version of the 1.2.8 XMLLayout that adds <log4j:MDC><log4j:data name="key" value="value"/></log4j:MDC> elements. Now that I check the cvs version (1.3alpha) of XMLLayout, I see the similar section dealing with MDC data commented out. Did I miss a discussion/decision on the dev list to change the 1.3 XMLLayout with regards to MDC data? If the latest chainsaw (or receiver) build is expecting something different, it may well be ignoring my MDC data. If I need to switch over to the dev list, let me know. I don't want to scare anyone away thinking chainsaw doesn't work... just keep in mind we were trying to leverege all the power of 1.3 while still being able to tell management we use only production-level 3rd party (oss) libraries. Thanks for the help, Scott D! I really appreciate it. -Scott Heaberlin --- Scott Deboy <[EMAIL PROTECTED]> wrote: > Hi Scott, > > Glad to hear you like it - > > MDC and the PROP keyword were consolidated > > If you change the tab identifier to > PROP.server.name, it should work. > > Let us know if this doesn't work or if you have > other questions. > > Scott ===== ============================== Scott Heaberlin [EMAIL PROTECTED] [EMAIL PROTECTED] ============================== --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
