You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2003/06/18 20:49:18 UTC
DO NOT REPLY [Bug 20886] New: -
web.xml: servlet param: fork==true results in no BuildException being thrown
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=20886>.
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=20886
web.xml: servlet param: fork==true results in no BuildException being thrown
Summary: web.xml: servlet param: fork==true results in no
BuildException being thrown
Product: Tomcat 4
Version: 4.1.24
Platform: PC
OS/Version: Linux
Status: NEW
Severity: Major
Priority: Other
Component: Jasper
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: light@sockeye.com
Linux Kernel: 2.4
java version 1.4.1_03
in /usr/local/tomcat/conf/web.xml you use the default (fork=true) setting, then
you don't get any BuildException from the compile phase and you only get an
Internal Error 500
org.apache.jasper.JasperException: Unable to compile class for JSP
at org.apache.jasper.JspCompilationContext.load(JspCompilationContext.java:500)
at
org.apache.jasper.servlet.JspServletWrapper.getServlet(JspServletWrapper.java:150)
....
which comes from the fact that it couldn't find a .class file.
you don't get the nice compiler error showing you where the problem in your code
was.
if you have in your /usr/local/tomcat/conf/web.xml the following:
<servlet>
<servlet-name>jsp</servlet-name>
<servlet-class>org.apache.jasper.servlet.JspServlet</servlet-class>
<init-param>
<param-name>logVerbosityLevel</param-name>
<param-value>INFORMATION</param-value>
</init-param>
<init-param><!-- VERY IMPORTANT set to false otherwise, no compile errs -->
<param-name>fork</param-name>
<param-value>false</param-value>
</init-param>
<load-on-startup>3</load-on-startup>
</servlet>
Note that this does not seem to be a problem on windows boxes, nor on vanilla
Redhat 7.2 platforms. It only seems to happen on our systems which have a
Redhat 7.0 base with a new kernel.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org