Help coderanch get a
new server
by contributing to the fundraiser
  • 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
  • Ron McLeod
  • Paul Clapham
  • Devaka Cooray
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • paul wheaton
  • Henry Wong
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Tim Moores
  • Carey Brown
  • Mikalai Zaikin
Bartenders:
  • Lou Hamers
  • Piet Souris
  • Frits Walraven

Problem with remotely running the managed server...help neded?

 
Ranch Hand
Posts: 108
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi All,
i have a problem while running managed server from admin console through node manager. i followed the admin guide instuctions. when first time its running properly. when i stop and starts the managed server from admin console i am getting following error.
Starting WebLogic Server ....
Connecting to http://194.0.0.76:7001...
<Sep 13, 2002 3:44:57 PM IST> <Notice> <WebLogicServer> <Starting WebLogic Managed Server "MyServer2" for domain "mydomain">
<Sep 13, 2002 3:45:06 PM IST> <Notice> <WebLogicServer> <ListenThread listening on port 7003, ip address 194.0.0.76>
***************************************************************************
The WebLogic Server did not start up properly.
Exception raised: weblogic.management.configuration.ConfigurationException - with nested exception:
[javax.naming.CommunicationException [Root exception is java.net.ConnectException: No server found at T3://194.0.0.76:7001]]
javax.naming.CommunicationException. Root exception is java.net.ConnectException: No server found at T3://194.0.0.76:7001
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:309)
at weblogic.jndi.Environment.getContext(Environment.java:156)
at weblogic.jndi.Environment.getInitialContext(Environment.java:139)
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:950)
at weblogic.management.Admin.start(Admin.java:351)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:372)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException - with nested exception:
[javax.naming.CommunicationException [Root exception is java.net.ConnectException: No server found at T3://194.0.0.76:7001]]
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:959)
at weblogic.management.Admin.start(Admin.java:351)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:372)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
***************************************************************************
thanks in advance.
regards,
seenu
 
Seenu Reddy
Ranch Hand
Posts: 108
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Guys,
i solved this problem.
thanks and regards,
seenu
 
Ranch Hand
Posts: 2713
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
What was the problem?
 
Seenu Reddy
Ranch Hand
Posts: 108
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
hi,
i have done two mistakes here.
1. in managed server, the nodemanager script i didn't add the some of the parameters.
2.in managed server, u have to enter the trusted hosts(the admin server) in the file 'nodemanager.hosts'
regards
seenu
 
reply
    Bookmark Topic Watch Topic
  • New Topic