|
Tony, You might try changing the fork parameter to false in your web.xml file -- later versions of Tomcat on the iSeries don't like the default. Here is what it looks like: <servlet> <servlet-name>jsp</servlet-name> <servlet-class>org.apache.jasper.servlet.JspServlet</servlet-class> <init-param> <param-name>logVerbosityLevel</param-name> <param-value>WARNING</param-value> </init-param> <init-param> <param-name>reloading</param-name> <param-value>false</param-value> </init-param> <init-param> <param-name>fork</param-name> <param-value>false</param-value> </init-param> <load-on-startup>3</load-on-startup> </servlet> David Morris >>> trichardson@xxxxxxxxxx 5/28/2004 5:55:48 AM >>> We've just installed Tomcat on our new iSeries 810 in a ifs directory, and I'm getting these strange page compile errors. The weird thing is you get the error on the first two hits on the page and on the third attempt it finally compiles. I've been using tomcat on Linux machines for the past couple of years and never ran into this error before. I'm sure it's a setup thing so maybe someone can help me out. To set this up I did the following: 1.. Uploaded the tomcat zip file to the iSeries IFS 2.. Ran the optimization job 3.. Setup a shell script to set the java home and catalina home environment variables 4.. Submitted a job to batch to call the shell script via qshell This is the error I'm getting: org.apache.jasper.JasperException: Unable to compile class for JSP An error occurred at line: -1 in the jsp file: null Generated servlet error: [javac] Compiling 1 source file at java/lang/Throwable.<init>(Throwable.java:195) at java/lang/Exception.<init>(Exception.java:41) at javax/servlet/ServletException.<init>(ServletException.java:107) at org/apache/jasper/JasperException.<init>(JasperException.java:73)... Thanks, Tony Richardson
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.