DeployAD4JManager Fails : Starting Server EMAD4JMANAGER ... Could Not Connect To Nodemanager (Doc ID 1209447.1)

Last updated on JULY 15, 2016

Applies to:

Enterprise Manager Base Platform - Version 11.1.0.1 to 11.1.0.1 [Release 11.1]
Information in this document applies to any platform.
***Checked for relevance on 15-Jul-2016***

Symptoms

JVM Diagnostics in EM Grid Control 11g

Running DeployAD4JManager script fails with error:

Starting an edit session ...
Started edit session, please be sure to save and activate your
changes once you are done.
Creating Server

Created Server. Now setting up properties

Saving all your changes ...
Saved all your changes successfully.
Activating all your changes, this may take a while ...
The edit lock associated with this edit session is released
once the activation is completed.
Activation completed

Starting server EMAD4JMANAGER ...Connection refused. Could not connect to NodeManager. Check that it is running at udMachine018.us.com:7401
No stack trace available.
This Exception occurred at Tue Aug 31 18:59:17 GMT+00:00 2010.
weblogic.management.scripting.ScriptException: Error occured while performing start : Server with name EMAD4JMANAGER failed to be started
at weblogic.management.scripting.ExceptionHandler.handleException(ExceptionHandler.java:48)
at weblogic.management.scripting.LifeCycleHandler.startServer(LifeCycleHandler.java:501)
at weblogic.management.scripting.WLScriptContext.start(WLScriptContext.java:477)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.python.core.PyReflectedFunction.__call__(Unknown Source)
at org.python.core.PyMethod.__call__(Unknown Source)
at org.python.core.PyObject.__call__(Unknown Source)
at org.python.core.PyObject.invoke(Unknown Source)
at org.python.pycode._pyx16.start$80(<iostream>:1270)
at org.python.pycode._pyx16.call_function(<iostream>)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyFunction.__call__(Unknown Source)
at org.python.pycode._pyx15.f$0(/opt/oracle/product/Middleware/oms11g/ad4j/DeployAD4JManager.py:87)
at org.python.pycode._pyx15.call_function(/opt/oracle/product/Middleware/oms11g/ad4j/DeployAD4JManager.py)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyCode.call(Unknown Source)
at org.python.core.Py.runCode(Unknown Source)
at org.python.util.PythonInterpreter.execfile(Unknown Source)
at weblogic.management.scripting.WLST.main(WLST.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.WLST.main(WLST.java:29)
java.lang.Exception
Error deploying jam manager

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms