How one can Repair java.lang.VerifyError: Anticipating a stack map body at department goal 14 in methodology at offset JDK 7 [Solved]

Howdy guys, at this time, we’ll check out the not-so-common error for Java functions. If in case you have been working in Java for a few years you then might need seen this dreaded “java.lang.VerifyError: Anticipating a stack map body at department goal 14 in methodology at offset JDK 7” error in your software log or in Eclipse, notably in case you are operating your Java software in Java 7. The primary explanation for this error, “java.lang.VerifyError: Anticipating a stack map body at department goal … within the methodology … at offset 0 error comes when you’ve gotten some library, JAR file which is just appropriate with Java 1.6 or beneath and you’re operating your program in JDK 1.7.

Clarification

Java 7 launched a stricter verification and adjusted the category format a bit to include a stack map, used to confirm that code is appropriate. The exception you see implies that some methodology does not have a sound stack map.

Java model or bytecode instrumentation might each be blame. Often, which means that a library that the appliance makes use of generates invalid bytecode that does not cross the stricter verification. So nothing else than reporting it as a bug to the library could be achieved by the developer.

As a workaround, you can too add -noverify to the JVM arguments with a view to disable verification. 

In Java 7 it was additionally potential to make use of -XX:-UseSplitVerifier to make use of the much less strict verification methodology of the earlier model which might deal with these lacking stack map frames, however that possibility can also be eliminated in Java 8.

Answer

In case you are operating in Java 7 then there are two options:

1) Simply use JDK 1.6, it is not going to do strict bytecode verification as JDK 7 however hey we’ve got been operating it for a very long time, so no situation.

2) Should you do not wish to downgrade on Java 1.6 and are fairly joyful operating with Java 1.7 then add -XX:-UseSplitVerifier into your record of JVM arguments which you’re passing to your Java program. Did you discover the “-” register entrance of UseSplitVerifier? That is really telling JVM to do not use that bytecode verifier.

In case you are utilizing Eclipse, you possibly can add this JVM argument as follows :

Home windows, Preferences, Java, Put in JREs, Edit, Default VM arguments

In case you are new to Eclipse and wish to be taught extra about it, you can too try Eclipse Tutorial For Rookies: Study Java IDE in 10 Steps, one other free Eclipse course on Udemy. It is also a very good course to start out studying Eclipse from scratch.

See stack hint right here :

java.lang.VerifyError: Anticipating a stackmap body at department goal 14 in methodology 
gwtone.server.TestServlet.doGet(Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet
/http/HttpServletResponse;)V at offset 0
    at java.lang.Class.getDeclaredConstructors0(Native Technique)
    at java.lang.Class.privateGetDeclaredConstructors(Unknown Supply)
    at java.lang.Class.getConstructor0(Unknown Supply)
    at java.lang.Class.newInstance0(Unknown Supply)
    at java.lang.Class.newInstance(Unknown Supply)
    at org.mortbay.jetty.servlet.Holder.newInstance(Holder.java:153)
    at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:428)
    at org.mortbay.jetty.servlet.ServletHolder.getServlet(ServletHolder.java:339)
    at org.mortbay.jetty.servlet.ServletHolder.deal with(ServletHolder.java:487)

That is all about the way to repair java.lang.VerifyError in Java, notably the “java.lang.VerifyError: Anticipating a stack map body at department goal 14 in methodology at offset JDK 7” error.