The Virtual Machine in Java 7 uses a new type-checker (also known as StackMap Frames) and Oracle's JVM provides the -XX:-UseSplitVerifier to force the runtime to fallback to the old type verifier, don't use StackMapTable on Java7. As you know this setting is specific to Java version and it's deprecated from Java 8 onwards.
I tried implementing this setting and couldn't get my 7.1.9 instance working. I think it will not work as there seems to be a conflicts/verifications errors on all the autogenerated/assembled classes.
Integration can you please confirm that the below issue is caused by a parameter which makes Java run in an unsupported version?
In the Platform Support Guide, you will find the following table of Pega 7.x version support for different Java versions:-
As you can see, Pega 7.1.9 supports Oracle Java 7 and 8, but does not support Oracle Java 6.
If GCS understanding is correct, the use of the -XX:-UseSplitVerifier with Oracle Java 7 reverts back to a Java 6 mode (“old verifier” instead of Oracle 7 “StackMap”):-
Assuming this is the case, given Pega 7.1.9 does not support for Oracle Java 6, we do not believe the -XX:-UseSplitVerifier option will be a supported option (the OOTB Pega classes having presumably been compiled in at least a Java 7 format)
---> Can an SME let us know if the user will need to run the instances which host Pega 7.1.9 without said -XX:-UseSplitVerifier option to be in a supported state?
I think the general response is that we don't test every combination of every -X option provided by every JVM vendor and unless we explicitly say one is supported, switches are to be used at the customer's discretion.
I don't know the details of this switch or why it wouldn't work.
May be this issue is due to generated code target (or manipulation)?
Actually, Pega 7 works with JDK 6 (that is correctly not supported as Oracle does not support it anymore) thus the compiler is able to generate JDK 6 compatible code (the JDK 6 verifier does not fail).
When running Pega 7 with JDK 7 possibly the compiler generates code that is only compatible with JDK 7 verifier, this makes this JVM option not working.