I think it is high time for Jmeter to come out of the dark ages of using
System.out as its "logging" implementation. It severely limits its
ability
to have more accurate samples as logs to System.out are blocking, and
they
take a comparatively long time.
There are a number of acceptable logging packages like LogKit and Log4J.
Since we are already using the avalon-framework.jar for the
Configuration
class, we can also use its logging abstraction to write the logs. It's
up to you guys to choose the logging package.
In order to get started, we can use the ConsoleLogger or the NullLogger
implementations so that we can figure out how to get the Logger instance
everywhere it needs to be. Then we can replace that with the real
logging
implementation.
It may be that a migration has started, but the last time I checked
(which,
admittedly was a while ago) there were many cases of
System.out.println()
in the code.
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
