• 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
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Problems running adminclient remotely

 
Ranch Hand
Posts: 271
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
We installed was 4.04 on a Redhat 8.0 box, we're using as a testbox.Trying to run adminclient on that box , remotely by doing
adminclient <testbox name>
from a any other machine on our network(Window and Linux boxes) , gives an error maessage saying
A communication error occured.
Caught exception while getting initial context:javax.namimg.CommunicationException:Caught CORBA.COMM_FAILURE when resolving initial reference=WsnNameService [Root exception is org.omg.CORBA.COMM_FAILURE: minor code: 3 completed: No]
Check misspelled hostname or hostname case for admin server
Well , we have checked the hostname , and even used its ip address as the argument to the adminclient command , but still get the same error message.We can ping the box though?
We have also tried
adminclient <ip address of testbox> 900 , but still get the same error.Port 900 is open , because doing a
telnet <ip address of testbox> 900 , establishes a connection.
What are we missing?
jeff mutonho
 
Ranch Hand
Posts: 219
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Jeff,
Sorry.. back with a question from this forum now..
Are you using WorkLoadManagement by any chance...
also ..
could you please post the first 3 lines from your admin.config
file from the application server ( the RH8 box).
Chances are that you have specified a value for the following
parameter:
com.ibm.ejs.sm.adminServer.nodeName
Check that this is spelt correctly, case sensitivity, if it is a name then check that the hosts file has an entry resolving it to the correct IP.
[ August 29, 2003: Message edited by: Nagendra Prasad ]
 
jeff mutonho
Ranch Hand
Posts: 271
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Nagendra
>Are you using WorkLoadManagement by any chance...
How would I tell this?

Here are the first 3 lines from the admin.config file
com.ibm.ejs.sm.adminServer.earFile=/opt/WebSphere/AppServer/config/admin.ear
com.ibm.ejs.sm.adminserver.classpath=/opt/WebSphere/AppServer/properties:/opt/WebSphere/AppServer/lib/bootstrap.jar
com.ibm.ejs.sm.adminServer.traceFile=/opt/WebSphere/AppServer/logs/tracefile
>Chances are that you have specified a value for the following
>parameter: com.ibm.ejs.sm.adminServer.nodeName
I searched in the whole admin.config file but didnt find thatr parameter.
We have another linux box , running RH7.2 and we can run the adminclient on that box remotely with no problems.The admin.config file for that box also does not specify the
com.ibm.ejs.sm.adminServer.nodeName parameter.
Thanx
 
Nagendra Prasad
Ranch Hand
Posts: 219
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Work Load management is when u have a clustered environment of WebSphere servers. It looks like it is not the case.
If servers are clustered, one server needs to to tell the other member something about their identitity. Each of the nodes in the cluster would have identify themselves.. and this is done by the parameter that I mentioned.
But that is off the topic we have here which is an error with
'Check misspelled hostname or hostname case for admin server'
That indicates that your adminclient is not able to talk to the server.
Does this error happen on the client machine or do you seen this error on
the server?
Does the admin server trace file say anything more?
this would be in APPSERVER_ROOT/logs directory on the Linux box.
Check if the admin server had started successfully...

the log file would look something like this:


I shall be checking this post often.. so please do let me know.
 
jeff mutonho
Ranch Hand
Posts: 271
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanx
Yes the admin server starts successfully and it does say it's ready for e-business .
I can run adminclient locally on the RH8 box , just not remotely(i.e from my windows machine).
We have another test box running RH7.2 and on it , I can run the adminclient remotely(from my Windows machine) , without any problem.The problem seems to be just specific to the RH8 box

I checked this file
/opt/WebSphere/AppServer/logs
and it's empty\
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic