Title	NullPointerException thrown when any page is accessed
Date	03-Dec-2004 19:57:13 EET
Version	2.1.86-alpha
Submitter	24.237.20.168
Criticality	MediumBug
Browser version	Firefox 1.0
Status	ClosedBug
PageProvider used	any
Servlet Container	tomcat 5.0.25
Operating System	Linux kernel 2.4.9-6
URL	http://test.kepler-project.org
Java version	1.4.2_06

Accessing any page on the wiki produces this output:

Error Message An unknown exception java.lang.NullPointerException was caught by Error.jsp. Exception java.lang.NullPointerException Place where detected com.ecyrd.jspwiki.WikiEngine.doPreTranslateFiltering(), line 1326

This wiki had been running successfully for a month, and another based on the same code in the same tomcat container has been running successfully for 6+ months (and is still running today at http://seek.ecoinformatics.org). I've made no changes to the wiki itself since then. When I tried to change the hostname under which it was running from test.kepler-project.org to www.kepler-project.org by reconfiguring tomcat, this exception began. I reconfigured tomcat to go back to using the original hostname (test.kepler-project.org) but the exception persists. My uninformed guess is that the site is not initializing properly, but I can't figure out how to debug the situation further. The tomcat logs show nothing unusual occuring. What is the purpose of the doPreTranslateFiltering() method?

At a minimum, I think that the NullPointerException that is being thrown is a bug -- a more informative exception should be thrown instead.

Well, JSPWiki does not throw NPE on purpose :). It would be very useful to get the stack trace and the jspwiki log files (see jspwiki.properties where they are generated) for a better analysis, otherwise I'm just guessing, since it's almost impossible to debug something that cannot be repeated.

The doPreTranslateFiltering method is related to jspwiki filters. Since you probably haven't configured any, I would need a complete stack trace to see where it really occurs.

-- JanneJalkanen

This is likely caused by a mistyped path name (or a non-existing path) in the configuration file. Please check your configuration carefully.

-- JanneJalkanen

--HarryMetske