Thank you for the very prompt and informative replies. They have been
very helpful indeed and pointed me towards a few other things to try.
--- Ceki Gülcü wrote:
> Is this log4j 1.2 or 1.3?
I was using log4j 1.2.9. I followed your suggestion and went ahead to
try 1.3-alpha6, and tried a similar
Is this log4j 1.2 or 1.3?
At 08:41 PM 2/24/2005, Chris Nash wrote:
Hi there,
I'd like to share a cautionary take about using an ObjectRenderer which
I hope people might find useful. I'm using log4j-1.2.9 not only for my
developer-level logging but also for a localized, end-user log, much in
the sam
It's a bug I am current working on. The recent changes in the Appender
interface relate to this problem.
At 09:20 PM 2/24/2005, James Stauffer wrote:
I encountered a similar problem and my code was endlessly recursive.
In my instance:
Database pool code logged to log4j
logj sent errors to a custo
I encountered a similar problem and my code was endlessly recursive.
In my instance:
Database pool code logged to log4j
logj sent errors to a customer Database Appender
The Database Apppender used the same Database pool code.
So if there was a connection problem it would be endlessly recursive.
No
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 renderer
Hi there,
I'd like to share a cautionary take about using an ObjectRenderer which
I hope people might find useful. I'm using log4j-1.2.9 not only for my
developer-level logging but also for a localized, end-user log, much in
the same way as discussed in the "Backend l10n" thread on this list. I
