DO NOT REPLY [Bug 18494] - velocityEngine.init opens velocity.log multiple times

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18494>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18494

velocityEngine.init opens velocity.log multiple times





------- Additional Comments From peter@peterryan.net  2003-08-20 19:07 -------
I am able to replicate this error although I only experience 1 file pointer to 
velocity.log for each instance of Velocity Engine (w2k jdk1.3.1) and not the 
reported 9 pointers / engine.

This error occurs when velocity is invoked without properties 
(velocityEngine.init()) and the default AvalonLogSystem is created. The problem 
is that each engine retrieves the same logFile name from the RuntimeService and 
creates a FileTarget velocity.log.

My assumption is properly specifying properties for each engine would correctly 
avoid this.

In addition to the negative behavorior described by Hendrik it also has the 
negative side effect that if I invoke VelocityEngine with  no properties, I 
will lose log messages from all but one of the engines (I have not investigated 
which one, likely the first or last engine invocation).

Does anyone have a thought for a better behaved defautlt logger? 

On another project I had a singleton default logger that I would default to if 
logging was incorrectly setup. It works well and avoids duplicate file pointers 
resulting in lost log messages. In the case where the default (Avalon?) is 
invoked or Avalon is specified with no properties (I don't even know if that is 
possible...I haven't investigated) the defaultLogger would be returnedto the 
calling VelocityEngine...maintaining only one gateway to velocity.log.

Peter Ryan