DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG� RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=33695>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND� INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=33695 Summary: Logger error with multiple Velocity engines Product: Velocity Version: 1.4 Platform: PC OS/Version: Windows 2000 Status: NEW Severity: normal Priority: P2 Component: Source AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] 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. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
