The tomcat benchmark intentionally triggers a NullPointerException and then uses its 'getMessage()' result as part of the verification hash. This fails with our VM since we provide a message which method was invoked on a null object. We find that helpful to find problems in chained methods like a().b().c().
It would be better to remove this dependency.
Log in to post a comment.