Re: Logger error with multiple Velocity engines

[Will Glass-Husain]

Hi Andrea,
Thanks for the bug report.  Would you mind posting this on Bugzilla?
http://issues.apache.org/
There's a couple of issues with the log4j system (the others involve closing 
the Logger properly).  I'd like to work on them all at once after finishing 
current stuff.

Best,
WILL
----- Original Message ----- 
From: "Andrea Vaccaro" <[EMAIL PROTECTED]>
To: <velocity-user@jakarta.apache.org>
Sent: Monday, February 21, 2005 3:28 AM
Subject: Logger error with multiple Velocity engines

Hello,
we have found out that if you instance and init multiple engines, under some 
circumstances that are not yet clear, there is an error on the log4j logger.

For example the following code:
public static void main(String[] args) throws Exception
{
      VelocityEngine[] engines = new VelocityEngine[4];
       for (int i = 0; i < engines.length; i++)
       {
           VelocityEngine engine = new VelocityEngine();
           engine.setProperty(RuntimeConstants.FILE_RESOURCE_LOADER_PATH, 
"C:\\temp");
           engine.init();
       }
}

will generate 141 lines of the following error:
log4j:ERROR Attempted to append to closed appender named [null].
Debugging Velocity source code we noticed that all the engines add an 
appender to the same shared logger and sometime a null appender is added.
We are currently using Velocity 1.4 and Log4J 1.2.9.

Thanks in advance,
Andrea and Giannandrea
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]