File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes BEA/Weblogic and the fly likes problem while creating 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 "problem while creating Node Manager" Watch "problem while creating Node Manager" New topic
Author

problem while creating Node Manager

Anand Bhatt
Ranch Hand

Joined: May 30, 2007
Posts: 189
Hi,
With Administration console I have created one managed server named MagdServer-0.I have also created one machine named Nav_Machine-0.
While machine is being selected I clicked on Node Manager tab and fill the required test fields values like
Type:RSH
Listen Address: localhost
Listen Port:5556
Node Manager Home: and Shell Command: left blanked.

After saving this when I am clicking "Monitoring-Node Manager Status" tab I am getting something like this:

Status: Inactive
Problem description: > NAVBHATT.corp.abc.com:Connection refused
Exception encountered while communicating with this node manager. Version: (not available) .

Please let me know where I am wrong while configuring the Machine.
Shikhar Madhok
Ranch Hand

Joined: Dec 18, 2006
Posts: 95
Hi Anand,

I was reading about Node Managers recently. As I understand it, the node manager should be running as a service on you system. You will not be able to start it from your server. Instead it should already be up and running when you start your server or when you try to communicate to it from your server.
I think what you have done is created a server and machine. But have not installed or started the node manager. Hence you are getting this error.
I hope someone who has already worked on Node Manager will be able to comment better.

HTH
Shikhar


He who asks a question is a fool for five minutes; he who does not ask a question remains a fool forever - Chinese proverb
Anand Bhatt
Ranch Hand

Joined: May 30, 2007
Posts: 189
Anyone know how or from where to start Node Manager?
Anand Bhatt
Ranch Hand

Joined: May 30, 2007
Posts: 189
Hi Shikhar,
Now I can run the managed server using the node manger.
What I was forget to do is that:Node Manager communicates with Managed Servers and Administration Servers using two-way SSL, I was using RSH type instead of SSL.
And to run the node manager from command prompt use :

WL_HOME\weblogic92\server\bin and run startNodeManager.cmd.
Shikhar Madhok
Ranch Hand

Joined: Dec 18, 2006
Posts: 95
Great. I did not know that. Something I learnt today.

Thanks
Shikhar
Harikrishna Gorrepati
Ranch Hand

Joined: Sep 23, 2010
Posts: 422
Hi, I tried this command in the console..But I am getting this error..Any idea ?

c:\Oracle100\Middleware\wlserver_10.0\server\bin>startNodeManager.cmd

<May 21, 2011 8:49:51 PM> <SEVERE> <Fatal error in node manager server>
java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
at java.net.ServerSocket.bind(ServerSocket.java:319)
at java.net.ServerSocket.<init>(ServerSocket.java:185)
at java.net.ServerSocket.<init>(ServerSocket.java:141)
at javax.net.ssl.SSLServerSocket.<init>(SSLServerSocket.java:84)
at javax.net.ssl.impl.SSLServerSocketImpl.<init>(Unknown Source)
at javax.net.ssl.impl.SSLServerSocketFactoryImpl.createServerSocket(Unknown Source)
at weblogic.nodemanager.server.SSLListener.init(SSLListener.java:72)
at weblogic.nodemanager.server.NMServer.start(NMServer.java:200)
at weblogic.nodemanager.server.NMServer.main(NMServer.java:339)
at weblogic.NodeManager.main(NodeManager.java:31)


OCPJP 6.0-81% | Preparing for OCWCD
http://www.certpal.com/blogs/cert-articles | http://sites.google.com/site/mostlyjava/scwcd |
anandraj tadkal
Ranch Hand

Joined: Feb 22, 2011
Posts: 98

Hi Hari,

The error indicates that there is some other process that has already locked the port on which you want to start the Nodemanager. And hence, it is unable to bind to that port.

Can you verify that?

By default, NodeManager run on port 5556.


Regards,
Anandraj
http://weblogic-wonders.com
Follow us on facebook:
https://www.facebook.com/weblogicwonders
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: problem while creating Node Manager