E1: WLS: After Upgrading JDK Used by Weblogic 12cR1 (12.1), Node Manager Is Failing to Start Through startNodeManager.cmd/startNodeManager.sh Script or From Windows Service
(Doc ID 2989244.1)
Last updated on NOVEMBER 27, 2023
Applies to:
JD Edwards EnterpriseOne Tools - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
When attempting to start Node Manager either by calling startNodeManager.cmd/startNodeManager.sh script or from Windows Service, Node Manager is not started and the following error is shown in the console:
Steps to replicate:
1. Start node manager by running the startNodeManager.cmd/startNodeManager.sh from bin folder under the Weblogic domain
2. The Node Manager fails to start with the above error
Changes
The JDK used by Weblogic has been upgraded from Oracle JDK 1.7.0_15+ to 1.8.0+
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 |
Changes |
Cause |
Solution |
References |