jQuery in Action, 3rd edition
The moose likes BEA/Weblogic and the fly likes unable to connect WLST to Node Manager Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » BEA/Weblogic
Bookmark "unable to connect WLST to Node Manager" Watch "unable to connect WLST to Node Manager" New topic

unable to connect WLST to Node Manager

nlr reddy

Joined: Jul 05, 2009
Posts: 9

Using nmConnect() command I was trying to connect WLST to Node Manager but unable to do so.

I get the following error if I give the following command

wls:/offline> nmConnect('weblogic', 'weblogic', 'localhost', '5556', 'base_domain', 'C:\bea9\user_projects\domains\base_domain', 'ssl')

Connecting to Node Manager ...
Traceback (innermost last):
File "<input>", line 1, in ?
File "<iostream>", line 1499, in nmConnect
WLSTException: 'Error occured while performing nmConnect : Cannot connect to the
Node Manager.I/O error while reading domain directory: java.io.IOException: C:\
\bea9\\weblogic90\\common\\bin\\\bea9\\user_projects\\domains\base_domain: The f
ilename, directory name, or volume label syntax is incorrect Use dumpStack() to
view the full stacktrace'

I also tried dumpStack(), this is the message I got

wls:/offline> dumpStack()
This Exception occured at Mon Jul 06 02:30:32 GMT 2009
weblogic.nodemanager.NMException: I/O error while reading domain directory: java
.io.IOException: C:\bea9\weblogic90\common\binea9\user_projects\domainase_domain
: The filename, directory name, or volume label syntax is incorrect
at weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClie
at weblogic.nodemanager.client.NMServerClient.connect(NMServerClient.jav
at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerCli
at weblogic.nodemanager.client.NMServerClient.getVersion(NMServerClient.
at weblogic.management.scripting.NodeManagerService.verifyConnection(Nod
at weblogic.management.scripting.NodeManagerService.nmConnect(NodeManage
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[
Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;
I)Ljava.lang.Object;(Unknown Source)
at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java
at org.python.core.PyMethod.__call__(PyMethod.java:96)
at org.python.core.PyObject.__call__(PyObject.java:248)
at org.python.core.PyObject.invoke(PyObject.java:2016)
at org.python.pycode._pyx2.nmConnect$93(<iostream>:1487)
at org.python.pycode._pyx2.call_function(ILorg.python.core.PyFrame;)Lorg
at org.python.core.PyTableCode.call(PyTableCode.java:208)
at org.python.core.PyTableCode.call(PyTableCode.java:404)
at org.python.core.PyFunction.__call__(PyFunction.java:184)
at org.python.core.PyObject.__call__(PyObject.java:248)
at org.python.pycode._pyx22.f$0(<input>:1)
at org.python.pycode._pyx22.call_function(ILorg.python.core.PyFrame;)Lor
at org.python.core.PyTableCode.call(PyTableCode.java:208)
at org.python.core.PyCode.call(PyCode.java:14)
at org.python.core.Py.runCode(Py.java:1135)
at org.python.core.Py.exec(Py.java:1157)
at org.python.util.PythonInterpreter.exec(PythonInterpreter.java:148)
at org.python.util.InteractiveInterpreter.runcode(InteractiveInterpreter
at org.python.util.InteractiveInterpreter.runsource(InteractiveInterpret
at org.python.util.InteractiveInterpreter.runsource(InteractiveInterpret
at weblogic.management.scripting.WLST.main(WLST.java:130)

Could you guys tell me what could be the error?

Any help is appreciated

Marcos Maia
Ranch Hand

Joined: Jan 06, 2001
Posts: 977

check is your domain is registered with nodemanager at nodemanager.domains file.
You can also take a look at a script I have written for starting servers with nodemanager at:


The post is in portuguese(I'm from Brazil) but you may be able to understand the script. It uses a properties file to load the variables wich you will also find in the post.

Other thing is, unless extremely necessary I start node manager using plain socket connection because configuring it to use ssl is a pain in ....

I agree. Here's the link: http://aspose.com/file-tools
subject: unable to connect WLST to Node Manager
It's not a secret anymore!