Do Not Disable Bytecode Verification to Avoid a java.lang.VerifyError (Doc ID 1291169.1)

Last updated on APRIL 16, 2024

Applies to:

Symptoms

For various reasons, you may have disabled the Java Bytecode Verifier by adding to your 'java' command line arguments one or both of the following JVM flags:

-Xverify:none 

-noverify

  For example:

• When running or compiling Java code, a java.lang.VerifyError might be encountered.  Various sources state that disabling the bytecode verifier is one method of avoiding the VerifyError.  
• Several documents in the internet recommend to disable Java bytecode verification for performance reasons.
• The bytecode verifier may have been disabled intentionally in order to execute bad classfiles; classfiles that would otherwise be rejected by the bytecode verifier.
• A third party may recommend disabling the bytecode verifier in various sources, .

Changes

The 'java' command argument -Xverify:none or -noverify or both is/are added to the 'java' command line or to a configuration file used to start a JVM, such that the JVM is launched with the bytecode verifier disabled.  For example:

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.