[VELOCITY-167] LogSystem NPE s

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.3.1
• Component/s: Engine
• Environment: Operating System: All; Platform: All
• Bugzilla Id: 19137
• Assignee: Unassigned
• Reporter: Jens Elkner
• Created: 18/Apr/03 09:41
• Updated: 11/Feb/11 11:23
• Resolved: 08/Mar/07 00:09

Description

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 ...