E1: SVM: Server Manager Console and Agent Issues With Oracle Java 1.8 Update 171 or Higher and IBM Java 220.127.116.11 or Higher
(Doc ID 2621953.1)
Last updated on JUNE 07, 2021
Applies to:JD Edwards EnterpriseOne Tools - Version 9.2 and later
Information in this document applies to any platform.
The following symptoms can be seen on the Server Manager Console and Agents:
- Server Manager Agents do not show up in Server Manager Console after install;
- Runtime metrics are not displayed for the managed instances;
- Server Manager Console self-update fails
- JAS and/or AIS Server Managed Instance page shows data missing under Instance Information.
The issue can manifest when using standalone E1 agents, embedded E1 agents and Server Manager which are using Oracle Java 1.8 Update 171 Or higher and IBM Java 18.104.22.168 or higher.
With Oracle Java 1.8 Update 171 Or Higher
In the SMC_Server_EOne_ManagementConsole1_Console.log file collected from the Weblogic server, the below errors are registered:
Secure Sockets Layer (SSL) 2.0, SSL 3.0, and Transport Layer Security (TLS) 1.0 which are using Cipher Block Chaining (CBC) encryption mode are disabled by default starting with Oracle Java 1.8 Update 171 and IBM Java 22.214.171.124 or higher.
This includes also 3DES_EDE_CBC which is used by default by Server Manager Management Console and E1 agents when communication is initiated on a secure JMX channel.
The 3DES_EDE_CBC algorithm is being added to the jdk.tls.disabledAlgorithms list with Oracle Java 1.8_171 and IBM Java 126.96.36.199 onward in java.security file.
Refer to the $jdk/jre/lib/security/java.security file of the Java installation being used by Weblogic or Websphere on which the Server Manager Console is installed, as well as the JDK being used by the Server Manager Agent and the managed instances:
jdk.tls.disabledAlgorithms=SSLv3, RC4, MD5withRSA, DH keySize < 1024, \ EC keySize < 224, DES40_CBC, RC4_40, 3DES_EDE_CBC (added with Oracle Java 1.8 Update 171 or higher and IBM Java 188.8.131.52 or higher)
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
|With Oracle Java 1.8 Update 171 Or Higher|
|With IBM Java 184.108.40.206 Or Higher|