weblogic.nodemanager.NodeManagerException

[Could not execute command start for server managedServer via the Node Manager - reason: [CommandInvoker: Failed to send command: 'online to server 'managedServer' to NodeManager at host: 'localhost:5555' with exception FATAL Alert:HANDSHAKE_FAILURE - The handshake handler was unable to negotiate an acceptable set of security parameters.. Please ensure that the NodeManager is active on the target machine].]

Solutions on the web16

  • [Could not execute command start for server managedServer via the Node Manager - reason: [CommandInvoker: Failed to send command: 'online to server 'managedServer' to NodeManager at host: 'localhost:5555' with exception FATAL Alert:HANDSHAKE_FAILURE
  • [Could not execute command start for server managedServer via the Node Manager - reason: [CommandInvoker: Failed to send command: 'online to server 'managedServer' to NodeManager at host: 'localhost:5555' with exception FATAL Alert:HANDSHAKE_FAILURE
  • via Oracle Community by 3004, 1 year ago
    [Could not execute command start for server server1 via the Node Manager - reason: [CommandInvoker: Failed to send command: 'online to server 'server1' to NodeManager at host: 'griffin.pn.egg.com:5555' with exception FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received.. Please ensure that the NodeManager is active on the target machine].]
  • Stack trace

    • weblogic.nodemanager.NodeManagerException: [Could not execute command start for server managedServer via the Node Manager - reason: [CommandInvoker: Failed to send command: 'online to server 'managedServer' to NodeManager at host: 'localhost:5555' with exception FATAL Alert:HANDSHAKE_FAILURE - The handshake handler was unable to negotiate an acceptable set of security parameters.. Please ensure that the NodeManager is active on the target machine].] at weblogic.nodemanager.NodeManagerRuntime.executeCommand(NodeManagerRuntime.java:472) at weblogic.nodemanager.NodeManagerRuntime.start(NodeManagerRuntime.java:76) at java.lang.reflect.Method.invoke(Native Method) at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:732) at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:714) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525) at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:952) at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:470) at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:198) at $Proxy86.start(Unknown Source) at weblogic.server.ServerLifeCycleRuntime.startServer(ServerLifeCycleRuntime.java:502) at weblogic.server.ServerLifeCycleRuntime.access$0(ServerLifeCycleRuntime.java:471) at weblogic.server.ServerLifeCycleRuntime$1.execute(ServerLifeCycleRuntime.java:423) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You are the first who have seen this exception. Write a tip to help other users and build your expert profile.