Problem 1: I think we'll need to see the code where you initialise the logger, and where you do the actual logging. Storing a local reference to the logger is fine, and the recommended practice. If you make it static, even better, I am not sure why you would want the GC to collect it.
Problem 2: I have seen this message myself and might be due to some code logging at the same time as the new properties are being applied. If the configuration effectively changes an appenders configuration, log4j must stop/close the old appender before creating a new instance with the new config. Paul On Fri, 2003-12-12 at 10:34, Shimi Avizmil wrote: > Anyone? I'm really lost here ... > > TIA > > > -----Original Message----- > > From: Shimi Avizmil > > Sent: Thursday, 11 December 2003 3:29 PM > > To: '[EMAIL PROTECTED]' > > Subject: Dynamic Configuration > > > > Hi all, > > I spent few hours going through the past messages, but I couldn't find an > > answer to my problems. > > Problem 1: > > I have few ejbs under weblogic that get the log throught getClass().getName() > > and keep a copy locally. (Not static) > > My first problem is that the log messages are appearing under incorrect class > > name, i.e. > > 14:39:11,701 [main] INFO ejbA - I'm ejb B > > Why is that? > > problem 2: > > I wrote a swing gui that you can load a new properties file remotely to my app > > on the weblogic server and it calls PropertyConfigurator.configure(props) with the > > new properties. After I do that I get a lot of ERRORS: trying to append to a > > closed appender... > > Why does that happen? is that because I cache the logger reference in stead of > > fetching it every time? > > should I make it static? if I'll make it static, will it effect the gc from > > collecting it? > > Thanks for the help. > > Cheers > > Shimi > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
