You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by bu...@apache.org on 2003/04/18 04:41:45 UTC
DO NOT REPLY [Bug 19137] New: -
LogSystem NPE s
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=19137>.
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=19137
LogSystem NPE s
Summary: LogSystem NPE s
Product: Velocity
Version: 1.3.1
Platform: All
OS/Version: All
Status: NEW
Severity: Minor
Priority: Other
Component: Source
AssignedTo: velocity-dev@jakarta.apache.org
ReportedBy: elkner@linofee.org
Unfortunately, the used LogSystem is unstable.
1) SimpleLog4JSystems:
- if runtime.log.logsystem.log4j.category is not set (default), the cast to
string throws an NPE, when trying to init(), i.e. obtain the categoryname.
- so first fix could be:
--
Object categoryname = o rsvc.getProperty("runtime.log.logsystem.log4j.category");
if ( categoryname != null )
{
logger = Logger.getLogger( categoryname.toString() );
...
---
- if null, same issue applies to the logfile stuff
- furthermore internalInit( logfile ) would throw an NPE from
java.io.FileOutputStream.<init>
- finally a log is there, but uninitialized (i.e. useless) and
- a misleading "PANIC: ..." message is thrown to stdout
almost the same counts for the Log4JLogSystem as well as the AvalonLogSystem ...
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org