• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Jeanne Boyarsky
  • Tim Cooke
Sheriffs:
  • Liutauras Vilda
  • paul wheaton
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Carey Brown
  • Frits Walraven
Bartenders:
  • Piet Souris
  • Himai Minh

Weblogic newbie question.

 
Greenhorn
Posts: 17
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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
 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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
 
If a regular clown is funny, then a larger clown would be funnier. Math. Verified by this tiny ad:
Free, earth friendly heat - from the CodeRanch trailboss
https://www.kickstarter.com/projects/paulwheaton/free-heat
reply
    Bookmark Topic Watch Topic
  • New Topic