JasperException in production

[Berneburg, Cris J. - US]

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)
[...]

So our current plan is upgrade Tomcat. Another message to follow about TC 8.5 compatibility problems, specifically cachingAllowed.

--
Cris Berneburg
CACI Lead Software Engineer

[Mark Thomas]

Post by Berneburg, Cris J. - US
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
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
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.

Post by Berneburg, Cris J. - US
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.

Post by Berneburg, Cris J. - US
Another message to follow about TC 8.5 compatibility problems, specifically cachingAllowed.

ACK.

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: users-***@tomcat.apache.org
For additional commands, e-mail: users-***@tomcat.apache.org

[Berneburg, Cris J. - US]

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-***@tomcat.apache.org
For additional commands, e-mail: users-***@tomcat.apache.org