Do Not Disable Bytecode Verification to Avoid a java.lang.VerifyError
(Doc ID 1291169.1)
Last updated on JULY 15, 2019
Applies to:Java SE JDK and JRE - Version 1.5.0 to 8
Oracle WebLogic Server - Version 10.3.6 and later
Information in this document applies to any platform.
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:
- 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, such as configuraiton/setup instructions, support instructions, and so on.
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:
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Do not compromise or disable Java's built-in security features.|