ADGU2008E error while attempting to connect to the administrative console
 Technote (FAQ)
 
Problem
With two WebSphere Application Server nodes in the same domain (multi-node), while attempting to connect to the Adminserver from the administrative console on one of the nodes, an ADGU2008E error occurs. The version and edition of both nodes are identical.

You might also see a CORBA COMM_FAILURE in the logs attempting to get a CORBA reference from 127.0.0.1 on port 9000.
.
The system32/etc/hosts file was set up as follows.
127.0.0.1 sample.cxm.
A similar case was reported in PMR 19796,004,000.
 
 
Solution
You can either delete the line in the system32/etc/hosts where 127.0.0.1 is mapped to the host.domain name or you can modify it to either:

127.0.0.1 localhost

or

<machine's ip address> host.domain

Explanation

ip address 127.0.0.1 is the default address for 'localhost'. If the etc/hosts file is left with this default:


127.0.0.1 localhost

then there are no problems. However, if the etc/hosts is modified so that the 'localhost' ip address is now mapped to a host.domain name, this can cause a problem with remote access. Because now you have assigned the 'localhost' ip address to the host.domain instead of 'localhost'.

This is similar to the problem reported in technote:
1000319 "Remote admin console fails with a ClassCastException".
You must be able to ping the adminserver from both the adminserver node and the remote admin console node and get the same results for both (pinging the domain.hostname from either machine should return the actual ip address of the adminserver node, not 127.0.0.1).

 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Administrative Console (all non-scripting)
Operating system(s): Windows
Software version: 4.0
Software edition:
Reference #: 1078458
IBM Group: Software Group
Modified date: Oct 8, 2003