On Feb 24, 2005, at 1:41 PM, Chris Nash wrote: ...
It turns out that the Appender (through the PatternLayout that was calling the renderer) was being called re-entrant. The translator object that my renderer was using was itself making log4j calls, which log4j components (like appenders or renderers) cannot do. It seems I would have to make sure any component I called in a renderer (or even in my toString() method) didn't log anything.
How can I avoid this? So far, the only idea I have had has been to put my renderer in a diagnostic context that I can later filter against to suppress the re-entrant logging calls, but that's surely not the right way to do it. For now I can get by with a much simpler toString() method, but I wondered if there was a more general solution.
Many thanks for your consideration
Were you seeing a deadlock on the logging within the renderers or some other issue? I have on my (lengthy) TO-DO list a fairly thorough analysis of LoggingEvent and rendering was one area that I thought was troubling.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
