[
https://issues.apache.org/jira/browse/VELOCITY-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henning Schmiedehausen closed VELOCITY-167.
-------------------------------------------
> LogSystem NPE s
> ---------------
>
> Key: VELOCITY-167
> URL: https://issues.apache.org/jira/browse/VELOCITY-167
> Project: Velocity
> Issue Type: Bug
> Components: Engine
> Affects Versions: 1.3.1
> Environment: Operating System: All
> Platform: All
> Reporter: Jens Elkner
> Assigned To: Velocity-Dev List
> Priority: Minor
>
> 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
> ...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
