Mark cjb> getting the dreaded JasperException in production. cjb> Don't know what changed to start causing this. Same cjb> thing happened in the test environment 9/4/18. We cjb> got around the problem in test by upgrading to Java cjb> 8u181 and Tomcat 8.5.30. cjb> cjb> JRE 8u171, 32 bit cjb> Tomcat 6.0.32, 32 bit cjb> cjb> org.apache.jasper.JasperException: Unable to compile class for JSP: cjb> An error occurred at line: 1 in the generated java file The type cjb> java.io.ObjectInputStream cannot be resolved. It is indirectly cjb> referenced from required .class files cjb> Stacktrace: cjb> at org.apache.jasper.compiler.DefaultErrorHandler.javacError cjb> (DefaultErrorHandler.java:92) cjb> [...]
mt> The short version is that there was an upgrade to the mt> Java version which exposed a known 'bug' in the Eclipse mt> compiler. That 'bug' was essentially that the version mt> of Tomcat (and hence the Eclipse compiler) was so old mt> it was not fully compatible with Java 8. OK, thanks for the explanation. cjb> So our current plan is upgrade Tomcat. mt> That should work. Thanks for confirming. You all have been telling me to upgrade for a while. :-) cjb> It should also be possible to fix this by replacing cjb> the ecj.jar in your existing Tomcat 6.0.x installation cjb> with a newer version. Good to know, just in case. Custom tweaks get lost easily, so this will be "Option B". -- Cris Berneburg CACI Lead Software Engineer --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
