Managed Servers of a Portal, Forms, Reports, Discoverer Installation Fail to Start with Java 7 with
Managed Servers of a Portal, Forms, Reports, Discoverer Installation Fail to Start with Java 7 with
Titleimage
Posted by Patrick Hamou on 2017:09:14 14:34:53
APPLIES TO:
Oracle Fusion Middleware - Version 11.1.2.1.0 and later
Oracle WebLogic Server - Version 10.3.5 to 10.3.5
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)
SYMPTOMS
Weblogic Server 10.3.6 Oracle Fusion Middleware 11.1.1.6 (and 11.1.1.7) - Classic Installation and Oracle Fusion Middleware 11.1.2.1 (and 11.1.2.2 (Forms and Reports). During the configuration, the WLS_Portal, WLS_Forms, WLS_Reports, or WLS_Discoverer may not be able to start, failing with this error:
Caused By: sun.security.pkcs11.ConfigurationException: Unknown keyword 'useEcX963Encoding', line 15
at sun.security.pkcs11.Config.parse(Config.java:425)
at sun.security.pkcs11.Config.<init>(Config.java:194)
at sun.security.pkcs11.Config.getConfig(Config.java:67)
at sun.security.pkcs11.SunPKCS11.<init>(SunPKCS11.java:110)
at sun.security.pkcs11.SunPKCS11.<init>(SunPKCS11.java:86)
Truncated. see log file for complete stacktrace
It appears to happen when trying to start managed servers which use Java 1.7.
The same issue can occur where Java 6 was used for the installation and then updated to Java 7. The managed servers fails to start. Depending on the version, it may be WLS_Portal, WLS_Forms, WLS_Reports, or WLS_Discoverer. It would depend on which one has satisfied the fix for the Java 7 certification.
CHANGES
Installed WLS using Java 7 or recently updated to Java 7
CAUSE
It is caused because JDK 7 is unable to initialize SunPKCS11 security provider as called from the WLS_Portal, WLS_Forms, WLS_Reports, or WLS_Discoverer managed server start up process.
SOLUTION
1) As a TEMPORARY workaround, manually edit the <jdk home>/jre/lib/security/java.security file to remove the SunPKCS11 provider:
from:
security.provider.1=sun.security.pkcs11.SunPKCS11 ${java.home}/lib/security/sunpkcs11-solaris.cfg
security.provider.2=sun.security.provider.Sun
security.provider.3=sun.security.rsa.SunRsaSign
...
to:
security.provider.1=sun.security.provider.Sun
security.provider.2=sun.security.rsa.SunRsaSign
...
Note once you remove the line you need to renumber the security providers so the first one is security.provider.1, the second one is security.provider.2 and so on.
2) Click on "retry" in the OUI. The operation should be successful this time.
3) This is TEMPORARY because you will later desire the security.provider.1=sun.security.pkcs11.SunPKCS11 you have commented out from <jdk home>/jre/lib/security/java.security. This workaround will allow the managed servers to start to finish the installation. If you later replace the Java to an updated release, (See Note 1492980.1), you will need to re-perform this each time. You will also not have the <jdk home>/jre/lib/security/java.security configured as per Java team. The final fix should be sought with WLS_Portal, WLS_Forms, WLS_Reports, or WLS_Discoverer teams ...depending on which one is failing. Once the correct version (or patch applied) for one of those, it should be able to start without this issue.
The following internal bugs have been filed to investigate the issue. Development has reviewed these bugs, and they have determined that they are not feasible to fix.
Bug: 18511809 - ORACLE FORMS AND REPORTS INSTALLATION FAILS WHILE STARTING MANAGED SERVER
Bug: 20191299 - WLS_FORMS SERVER START FAILS AFTER JDK UPGRADE TO 1.6.0_85 OR 1.7
Bug: 20190938 - PORTAL/FORMS/REPORTS START FAILS AFTER JDK UPGRADE TO 1.6.0_85 OR 1.7
Posted by Patrick Hamou on 2017:09:14 14:34:53