GeeCON Prague 2014*
The moose likes BEA/Weblogic and the fly likes SecureCommandInvoker: Could not create a socket to the NodeManager  in weblogic8.1 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Products » BEA/Weblogic
Bookmark "SecureCommandInvoker: Could not create a socket to the NodeManager  in weblogic8.1" Watch "SecureCommandInvoker: Could not create a socket to the NodeManager  in weblogic8.1" New topic
Author

SecureCommandInvoker: Could not create a socket to the NodeManager in weblogic8.1

Gopal Bhaskar
Greenhorn

Joined: Sep 30, 2010
Posts: 3

Hi all,

I had created one Admin server and two managed servers in my pre production environment in weblogic8.1.I had stopped both the servers intially from the console and tried to restart.

Managed2 was running but the Managed1 server was in suspended state.I had killed the process and now the state of the Managed1 is in unknown.
selected the start the server option and got the below error.


SecureCommandInvoker: Could not create a socket to the NodeManager running on host 't-bea-app1-ng:5555' to execute command 'online appserver1', reason: connect: Connection refused. Ensure that the NodeManager on host 't-bea-app1-ng' is configured to listen on port '5555' and that it is actively listening


Any idea why the error had occured.



Thanks in advance.
Gopal
Rajendra Nandam
Greenhorn

Joined: Oct 26, 2009
Posts: 8
Hi,

Please refer the CODERANCH which already discussed and will get some information from it.


Thanks
Nandam
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: SecureCommandInvoker: Could not create a socket to the NodeManager in weblogic8.1