aspose file tools*
The moose likes EJB and other Java EE Technologies and the fly likes Problems running adminclient remotely Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "Problems running adminclient remotely" Watch "Problems running adminclient remotely" New topic
Author

Problems running adminclient remotely

jeff mutonho
Ranch Hand

Joined: Apr 30, 2003
Posts: 271
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?
What are we missing?
jeff mutonho
Nagendra Prasad
Ranch Hand

Joined: Jul 11, 2002
Posts: 219
jeff.. this might have been a question for the websphere forum.
but here's a thought anyway..
u mentioned <adminclient> <hostname>
instead try
<adminclient> <host ip address> 900

900 is the port on which the admin server runs. This is critical as well.


Best Regards,<br />Nagendra Prasad.
jeff mutonho
Ranch Hand

Joined: Apr 30, 2003
Posts: 271
My apologies.I didn't realize there is indeed a websphere forum.
Thanx for the response.I will try it that and see what happens.I do know though that port 900 is open , because I did a
telnet testbox 900
and connected successfully.
jeff mutonho
Nagendra Prasad
Ranch Hand

Joined: Jul 11, 2002
Posts: 219
No worries reg. the forum Jeff.. some bartender could have noticed.. and moved it in the meantime...
Here's what we are doing..
C:\WebSphere\AppServer\bin\adminclient.bat 10.10.3.219 900

and it works.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Problems running adminclient remotely
 
Similar Threads
remote adminclient failing
AdminClient don't start
Problems running adminclient remotely
Exception in thread main
what are JMX Configuration required in WebSphere5.0 with JDK1.4/Sample Pmirm.xml