Java release issue after upgrade to WCC r11.4 SP7
Article ID: 194853
Updated On:
Products
Issue/Introduction
I am upgrading from WCC r11.4 SP6 to WCC r11.4 SP7 on RHEL7.
Prior to the upgrade, WCC r11.4 SP6 was working with a 64 bit java as follows:
java version "1.8.0_251"
Java(TM) SE Runtime Environment (build 1.8.0_251-b08)
Java HotSpot(TM) 64-Bit Server VM (build 25.251-b08, mixed mode)
After the upgrade to WCC r11.4 SP7, it will not work with that relesase of Java, although it will work with the release that upgrade lays in which is as follows:
java version "1.8.0_202"
Java(TM) SE Runtime Environment (build 1.8.0_202-b08)
Java HotSpot(TM) 64-Bit Server VM (build 25.202-b08, mixed mode)
Is there a reason why r11.4 SP7 is not working with java version 1.8.0_251?
Environment
Release : 11.3.6
Component : WORKLOAD CONTROL CENTER
Resolution
If you attempt to use your own JRE rather than the one WCC ships with you need to add the following entry:
security.provider.10=org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider
to the JRE's
%WCC_INSTALLATION%/jre/lib/security/java.security file.
FYI - you would need to do this for BOTH jre's assuming you would be adjusting both your 64 and 32 bit jre(s).
And if you already have a security.provider.10= entry in your file, please adjust the new entry to be the next number in the sequence...
meaning security.provider.11 or security.provider.12 etc...
WCC ships with the following settings:
security.provider.1=sun.security.provider.Sun
security.provider.2=sun.security.rsa.SunRsaSign
security.provider.3=sun.security.ec.SunEC
security.provider.4=com.sun.net.ssl.internal.ssl.Provider
security.provider.5=com.sun.crypto.provider.SunJCE
security.provider.6=sun.security.jgss.SunProvider
security.provider.7=com.sun.security.sasl.Provider
security.provider.8=org.jcp.xml.dsig.internal.dom.XMLDSigRI
security.provider.9=sun.security.smartcardio.SunPCSC
security.provider.10=org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider
Feedback
