This week's book giveaway is in the Servlets forum.
We're giving away four copies of Murach's Java Servlets and JSP and have Joel Murach on-line!
See this thread for details.
The moose likes BEA/Weblogic and the fly likes Weblogic newbie question. Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Products » BEA/Weblogic
Bookmark "Weblogic newbie question." Watch "Weblogic newbie question." New topic
Author

Weblogic newbie question.

Billy Fence
Greenhorn

Joined: Jul 17, 2003
Posts: 17
Hi,
Really hope someone out there can help me. I'm using standard weblogic 6.1 install with only one administration server 'myserver'. By default this is tied to machine (none), listens to 7001 and has an empty listen address. When I want to create a new logical server, for example one named applicserver I need to bind that to a machine. Since the machine listbox only shows me (none) I try that and start to run it. This is what happens:
<08-Aug-03 15:24:29 CEST> <Error> <NodeManager> <Could not start server 'wasp-adminserver' via Node Manager - reason: '[SecureCommandInvoker: Could not create a socket to the NodeManager running on host 'localhost:5555' to execute command 'online applicserver', reason: Connection refused: connect. Ensure that the NodeManager on host 'localhost' is configured to listen on port '5555' and that it is actively listening]'>

So I thought let's create a new machine and call that localhost that listens to another port, for example 7999. Then tried to bind the applicserver to that new machine and tried to start it. Again the above output. It drives me nutts. I don't have a helping hand close by and the weblogic documentation is too much to go through, so I'm stuck. Can anyone out there explain what I'm doing wrong.
Cheers
Billy
Marina Kuper
Greenhorn

Joined: Sep 02, 2004
Posts: 1
In order to start managed servers you should create Node Manager on the same machine, start this Node Manager running script startNodeManager, installed in WL_HOME\server\bin.After that rerun your admin server, chech the status of Node Manager on admin console and run your managed servers
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Weblogic newbie question.
 
Similar Threads
NodeManager problem
Problem starting ManagedServer via Nodemanager
SecureCommandInvoker: Could not create a socket to the NodeManager in weblogic8.1
Weblogic newbie question.
weblogic clustering for the multiple machines