As it happens, I just got a bit more information on the problem. The JVM
designations are what show up in Tomcat's Manager webapp.
Case "P"(fails): Tomcat 7.0.67 running under JVM 22.214.171.124 -
pap6480sr6-20191107_01(SR6), on OS V7R2M0
Case "S" (fails): Tomcat 7.0.56 running under JVM 126.96.36.199 -
pap6480sr6fp10-20200408_01(SR6 FP10), on OS V7R1M0, and the PTFs to
complete Java 8 installation were just installed this month.
Case "C" (works): Tomcat 7.0.93 running under JVM 188.8.131.52 -
pap6480sr5fp35-20190418_01(SR5 FP35), on OS V7R3M0
And it works just fine on our own V6 box, under Java 6, without needing
to apply any kind of java.security override.
I downloaded a copy of the java.security from case "P" for study.
Overrides have not been disabled.
This is the Java Programming on and around the IBM i (JAVA400-L) mailing
To post a message email: JAVA400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: JAVA400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
Help support midrange.com by shopping at amazon.com with our affiliate