My Oracle Support Banner

E1: SVM: Server Manager Console and Agent Issues With Oracle Java 1.8 Update 171 or Higher and IBM Java 8.0.4.1 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.

Symptoms

The following symptoms can be seen on the Server Manager Console and Agents:

These issues are specific to Server Manager Console 9.2.x installed on Weblogic Application Server with jdk version 1.8 Update 171 or higher. For iSeries and Websphere check Doc ID 2622074.1.

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 8.0.4.1 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:

 

Changes

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 8.0.4.1 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 8.0.4.1 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 8.0.4.1 or higher)

Cause

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
Symptoms
 With Oracle Java 1.8 Update 171 Or Higher
 With IBM Java 8.0.4.1 Or Higher
Changes
Cause
Solution
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.