aspose file tools*
The moose likes Websphere and the fly likes remote adminclient failing 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 » Products » Websphere
Bookmark "remote adminclient failing" Watch "remote adminclient failing" New topic
Author

remote adminclient failing

Jim Grecni
Greenhorn

Joined: Nov 06, 2002
Posts: 2
I'm trying to run adminclient from a remote system. It's failing trying to connect. The debug output shows:
ADGU1045E: Caught exception while getting initial context:"javax.naming.CommunicationException: Caught CORBA.COMM_FAILURE when resolving initial reference=WsnNameService [Root exception is org.omg.CORBA.COMM_FAILURE: minor code: 3 completed: No]
There is no firewall between my systems. I've tried running the adminclinet from both a NT and Linux systems with the same result.
The adminclient runs fine locally. The local system is RedHat Linux 8.0 with WAS 4.04.
I can telnet, ftp, ping and otherwise connect to the box running WebSphere.
Anyone have any suggestions?
Thank you.
Raj Varanasi
Greenhorn

Joined: Nov 20, 2001
Posts: 11
Hi,
Are you giving complete command like "adminclient.sh remotehostname bootstrapport" while invoking admin client from remote machine ?
Jim Grecni
Greenhorn

Joined: Nov 06, 2002
Posts: 2
Yes, I used the complete command
adminclient.sh hostname 900
I also tried defaulting the host number, same result. I also tried running the command on the local machine, specifically puting in the hostname and port number. It works from the local command.
I also tried connecting to port 900 using telnet, just to ensure the communications are working. I get connected.
I admit, I'm confused as to what's wrong.
Kyle Brown
author
Ranch Hand

Joined: Aug 10, 2001
Posts: 3879
I suspect a TCP (probably DNS) problem. Try adding the name of the remote host to your etc/hosts file on the client and then try with the fully qualified shell script (e.g. specifying the name and port).
Kyle


Kyle Brown, Author of Persistence in the Enterprise and Enterprise Java Programming with IBM Websphere, 2nd Edition
See my homepage at http://www.kyle-brown.com/ for other WebSphere information.
Patrick Finnegan
Ranch Hand

Joined: Mar 05, 2002
Posts: 179
How many network cards in the machine? WebSphere needs to be bound to one network card via the admin.config.
e.g
com.ibm.CORBA.LocalHost=192.168.200.111
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: remote adminclient failing
 
Similar Threads
Testing On Multiple Platforms
Problems running adminclient remotely
Problems running adminclient remotely
java.net.ConnectionException
AdminClient don't start