On 04/10/18 14:21, Berneburg, Cris J. - US wrote: > OK, now we're getting the dreaded JasperException in production. Don't know > what changed to start causing this. Same thing happened in the test > environment 9/4/18. We got around the problem in test by upgrading to Java > 8u181 and Tomcat 8.5.30. > > JRE 8u171, 32 bit > Tomcat 6.0.32, 32 bit > > org.apache.jasper.JasperException: Unable to compile class for JSP: > An error occurred at line: 1 in the generated java file > The type java.io.ObjectInputStream cannot be resolved. It is indirectly > referenced from required .class files > Stacktrace: > at > org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:92) > [...]
Googling for: "The type java.io.ObjectInputStream cannot be resolved. It is indirectly referenced from required .class files" returned a number of similar explanations: https://bugs.openjdk.java.net/browse/JDK-8155223 https://bugzilla.redhat.com/show_bug.cgi?id=1337940 The second of those is probably the clearest. The short version is that there was an upgrade to the Java version which exposed a known 'bug' in the Eclipse compiler. That 'bug' was essentially that the version of Tomcat (and hence the Eclipse compiler) was so old it was not fully compatible with Java 8. > So our current plan is upgrade Tomcat. That should work. It should also be possible to fix this by replacing the ecj.jar in your existing Tomcat 6.0.x installation with a newer version. > Another message to follow about TC 8.5 compatibility problems, specifically > cachingAllowed. ACK. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
