> >Without this fix or something like it, any mutable content in MDC will > >be carried across threads and will be subject to > >ConcurrentModificationExceptions at the least and the logging of > >incorrect context data since the context can change between the time the > >event was issued and the asychronous append.
Putting something that is mutable into the MDC is something that I don't think you really want to be doing is it? Wouldn't it be better to be storing an immutable Memento of the item's state in the MDC? If the item changes, isn't it easy to then replace the Memento in the MDC? Then if another Thread gets a copy of the MDC you won't have to worry, since the Memento is immutable. Could you give us some context as to why a mutable object is going into the MDC? That might give us more clues. cheers, Paul Smith --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
