SOACS - Scale Out Attempt Fails With The Error: Failed starting node manager with wait option
(Doc ID 2626439.1)
Last updated on AUGUST 12, 2024
Applies to:
SOA Suite Cloud Service - Version N/A and laterInformation in this document applies to any platform.
Symptoms
Steps to reproduce:
1. Scale-out the existing SOACS instance.
2. The actual scale-out completes successfully.
3. When the provisioning script attempts to start the Node Manager, on the new WLS-2 environment, it errors with "Failed starting node manager with wait option". This error appears in the Provisioning Log file.
The WebLogic Diagnostic log contains errors like:
[ERROR] [OSB-473078] Cannot contact Admin server. Therefore constructing the Cluster Authority Current time with the time skew 0[[java.rmi.RemoteException: ClusterTimerAuthority error; nested exception is: javax.naming.CommunicationException: Failed to initialize JNDI context, tried 2 time or times totally, the interval of each time is 0ms.
Destination unreachable.; nested exception is:java.net.ConnectException: Connection refused (Connection refused); No available router to destination.
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 |
| Cause |
| Solution |
| References |