kn> Thank you for your quick reply! In your initial bug report, you
kn> say you changed the default "in your environment". Did you have a
kn> way to do that without modifying the log4j source? I didn't see a
kn> way to do it without rebuilding log4j.
There were a few messages earlier in the thr
Thank you for your quick reply! In your initial bug report, you say you
changed the default "in your environment". Did you have a way to do
that without modifying the log4j source? I didn't see a way to do it
without rebuilding log4j.
-Kim.
WJCarpenter wrote:
kn> Background: We put a bunch o
kn> Background: We put a bunch of expensive operations in
kn> Logger.isDebugEnabled() if statements, and we had a customer
kn> complain about the performance. (The operations were in support
kn> of creating log messages.) We discovered that the customer was
kn> using a file called "log4j_properti
Hello,
My subject line is a summary of the issue, but in reality I think I know
what happens --- I'm basically looking for confirmation.
Background:
We put a bunch of expensive operations in Logger.isDebugEnabled() if
statements, and we had a customer complain about the performance. (The
opera
