Comment 2 for bug 1669093

Sorry but I don't have a test case since I'm not a java dev. I guess that a simple java webapp using that class compiled with jdk 1.8 may trigger the exception.

I just have a compiled java app from 3rd party to run at my server and I'm upgrading it (the OS).
I'm not sure that the exception comes from internals of tomcat or the app itself, the fact is that the tomcat 7 package behaves different from tomcat7 downloaded from apache.org with the same webapp. The same webapp works with tomcat7 package at a ubuntu trusty server.

It seems that a particular java class does not behave the same if compiled with java 8 even with compatibility with 1.6.