On Tue, 2006-02-21 at 17:59 +1300, Simon Kitching wrote:
> The Log4JLogger class appears to work correctly, because it implements
> getLogger like this:
> public Logger getLogger() {
> if (logger == null) {
> logger = Logger.getLogger(name);
> }
> return (this.logger);
> }
> which reinitialises the logger member after deserialization. Personally
> I would like to see a readObject method do this instead as all other
> methods could then access the logger member directly and avoid a method
> call; however both will work fine. Hmm..perhaps this method call is the
> cause of the slowdown in Log4JLogger since 1.2 revealed by Robert's
> recent tests?
i've tracked this down now. there appears to be big performance
difference between calling category and logger when the log system is
not configured. add a basic, no logging configuration brought the
figures all into line.
so, the good news is that we're about as fast as the other JCL
releases.
FWIW i also prefer the readObject solution
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
