|
Problem |
When attempting to open an administrative console to a
remote administrative server and it files obtain an administrative console
trace.
To do this you simply run the following command from the install_root\bin
directory:
adminclient debug hostname > absolutepath\client.txt
2>&1
Note: If using port other than 900 specify it by adding it after hostname.
Error seen from admin console trace:
[11/17/03 9:37:58:620 EST] 1befd6ef TypeTree W ADGU1038E: Failed to get
the type tree
[11/17/03 9:37:58:742 EST] 1befd6ef TypeTree W ADGU1039E: Failed to get
type information from access bean
[11/17/03 9:38:46:385 EST] 3f2056ed InstanceTree W ADGU1016E: Cannot
narrow a reference java.lang.NullPointerException
at
com.ibm.ejs.sm.client.InstanceTree.narrowStubRef(InstanceTree.java:443)
at com.ibm.ejs.sm.client.InstanceTree.insert(InstanceTree.java:230)
at
com.ibm.ejs.sm.client.InstanceTree.addRootInstances(InstanceTree.java:150)
at com.ibm.ejs.sm.client.InstanceTree$Loader.run(InstanceTree.java:579)
[11/26/03 11:58:13:312 EST] 1385d7d5 WsnInitCtxFac W NMSV0602E: Naming
Service unavailable. A communications error occurred.
[11/26/03 11:58:13:435 EST] 1385d7d5 RepositoryCli W 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]
[11/26/03 11:58:13:761 EST] 1385d7d5 RepositoryCli W ADGU1069A: Check
misspelled hostname or hostname case for admin server
[2/16/04 22:53:30:537 EST] c17b16d ORBRas X com.ibm.CORBA.iiop.Profile
JORB00106: In Profile.getIPAddress(), InetAddress.getByName(
server123.abc.companyX.com ) threw an UnknownHostException P=6418:O=0:CT
The following exception was logged
java.net.UnknownHostException: server123.abc.companyX.com
at java.net.InetAddress.getAllByName0(InetAddress.java(Compiled Code))
at java.net.InetAddress.getAllByName0(InetAddress.java(Inlined Compiled
Code))
at java.net.InetAddress.getByName(InetAddress.java(Compiled Code))
at com.ibm.CORBA.iiop.Profile.getHostIPAddress(Profile.java:340)
at
com.ibm.ISecurityLocalObjectBaseL13Impl.SecurityComponentFactory.create(SecurityComponentFactory.java:200)
at com.ibm.CORBA.iiop.ORB.iterateIORAccessorCreates(ORB.java:2807)
at com.ibm.CORBA.iiop.IOR.init(IOR.java:283)
at com.ibm.CORBA.iiop.IOR.<init>(IOR.java:164)
at
com.ibm.CORBA.iiop.InitialNamingClient.getInitialRep(InitialNamingClient.java:320)
at
com.ibm.CORBA.iiop.InitialNamingClient.resolve(InitialNamingClient.java:363)
at
com.ibm.CORBA.iiop.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:591)
at
com.ibm.CORBA.iiop.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:355)
at com.ibm.CORBA.iiop.ORB.resolve_initial_references(ORB.java:1877)
at
com.ibm.ws.naming.util.WsnInitCtxFactory.mergeWsnNSProperties(WsnInitCtxFactory.java:592)
at
com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnInitCtxFactory.java:354)
at
com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:229)
at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:98)
at com.ibm.ws.naming.util.WsnInitCtx.<init>(WsnInitCtx.java:79)
at
com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContext(WsnInitCtxFactory.java:137)
at
com.ibm.websphere.naming.WsnInitialContextFactory.getInitialContext(WsnInitialContextFactory.java:80)
at
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:674)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:255)
at javax.naming.InitialContext.init(InitialContext.java:231)
at javax.naming.InitialContext.<init>(InitialContext.java:187)
at
com.ibm.ejs.sm.client.RepositoryClient.<init>(RepositoryClient.java:241)
at com.ibm.ejs.sm.client.ui.EJSConsole.<init>(EJSConsole.java:476)
at com.ibm.ejs.sm.client.ui.EJSConsole.main(EJSConsole.java:1366)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:158)
[2/16/04 22:53:30:654 EST] c17b16d ORBRas X com.ibm.CORBA.iiop.Profile
JORB00106: In Profile.getIPAddress(), InetAddress.getByName(
server123.abc.companyX.com ) threw an UnknownHostException P=6418:O=0:CT
The following exception was logged
java.net.UnknownHostException: server123.abc.companyX.com
at java.net.InetAddress.getAllByName0(InetAddress.java(Compiled Code))
at java.net.InetAddress.getAllByName0(InetAddress.java(Inlined Compiled
Code))
at java.net.InetAddress.getByName(InetAddress.java(Compiled Code))
at com.ibm.CORBA.iiop.Profile.getHostIPAddress(Profile.java:340)
at
com.ibm.ISecurityLocalObjectBaseL13Impl.SecurityComponentFactory.create(SecurityComponentFactory.java:200)
at com.ibm.CORBA.iiop.ORB.iterateIORAccessorCreates(ORB.java:2807)
at com.ibm.CORBA.iiop.IOR.init(IOR.java:283)
at com.ibm.CORBA.iiop.IOR.<init>(IOR.java:164)
at
com.ibm.CORBA.iiop.InitialNamingClient.getInitialRep(InitialNamingClient.java:320)
at
com.ibm.CORBA.iiop.InitialNamingClient.resolve(InitialNamingClient.java:363)
at
com.ibm.CORBA.iiop.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:591)
at
com.ibm.CORBA.iiop.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:355)
at com.ibm.CORBA.iiop.ORB.resolve_initial_references(ORB.java:1877)
at
com.ibm.ws.naming.util.WsnInitCtxFactory.getCosRootContext(WsnInitCtxFactory.java:437)
at
com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnInitCtxFactory.java:363)
at
com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:229)
at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:98)
at com.ibm.ws.naming.util.WsnInitCtx.<init>(WsnInitCtx.java:79)
at
com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContext(WsnInitCtxFactory.java:137)
at
com.ibm.websphere.naming.WsnInitialContextFactory.getInitialContext(WsnInitialContextFactory.java:80)
at
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:674)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:255)
at javax.naming.InitialContext.init(InitialContext.java:231)
at javax.naming.InitialContext.<init>(InitialContext.java:187)
at
com.ibm.ejs.sm.client.RepositoryClient.<init>(RepositoryClient.java:241)
at com.ibm.ejs.sm.client.ui.EJSConsole.<init>(EJSConsole.java:476)
at com.ibm.ejs.sm.client.ui.EJSConsole.main(EJSConsole.java:1366)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:158)
[2/16/04 22:53:30:957 EST] c17b16d WsnInitCtxFac W NMSV0603E: Naming
Service unavailable. Could not get the root context.
[2/16/04 22:53:30:971 EST] c17b16d RepositoryCli W ADGU1045E: Caught
exception while getting initial
context:javax.naming.ServiceUnavailableException: Caught exception when
resolving initial reference=NameService [Root exception is
org.omg.CORBA.INTERNAL: JORB00106: In Profile.getIPAddress(),
InetAddress.getByName( server123.abc.companyX.com ) threw an
UnknownHostException minor code: 0 completed: No]
[2/16/04 22:53:30:993 EST] c17b16d RepositoryCli W ADGU1069A: Check
misspelled hostname or hostname case for admin server
[3/22/04 11:10:01:895 EST] 7c7af153 WsnInitCtxFac W NMSV0602E: Naming
Service unavailable. A communications error occurred.
[3/22/04 11:10:01:984 EST] 7c7af153 RepositoryCli W 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]
[3/22/04 11:10:02:225 EST] 7c7af153 RepositoryCli W ADGU1069A: Check
misspelled hostname or hostname case for admin server
[3/22/04 11:13:31:259 EST] 7c7ef0f5 WsnInitCtxFac W NMSV0602E: Naming
Service unavailable. A communications error occurred.
[3/22/04 11:13:31:343 EST] 7c7ef0f5 RepositoryCli W 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]
[3/22/04 11:13:31:585 EST] 7c7ef0f5 RepositoryCli W ADGU1069A: Check
misspelled hostname or hostname case for admin server
|
|
Cause |
Even though the stack trace tells us "Check misspelled
hostname or hostname case for admin server" there are several reasons that
can cause the above stack to occur including the wrong host name, spelling
issues, Domain Name Service (DNS) issues, etc. |
|
Solution |
It is recommended to work through the list in a top down
order and eliminate each possibility one at a time:
- Ensure you have entered the correct fully qualified remote server name
and port in your startup command and are starting it from the /bin
directory. For example:
- UNIX®:
install_root/bin/adminclient.sh
hostName portNumber
- Windows®:
install_root/bin/adminclient.bat
hostName portNumber
- Ensure the fully qualified remote server name is correctly defined in
your DNS.
- Ensure the local machine's hosts file has the IP address and fully
qualified remote server name listed. This file is located for
- UNIX:
/etc/hosts
- Windows:
C:\WINDOWS\system32\drivers\etc\hosts
- Ensure that you look similar to these:
127.0.0.1 loopback localhost
15.12.4.11 machinename.companyname.com localMachineName
16.12.4.11 remateserver.companyname.com remoteAdminServerName
- Repeat step 3 again but this time to the remote server's hosts file.
- Ensure you can ping and telnet to the remote server from the local
machine. This will ensure connection can be established between the two
machines outside of the WebSphere Application Server program.
- Can you resolve the hostname/IP address from the remote machine. If
you are using DNS to resolve server names, then perform the following
command from a command window similar to this Windows command:
nslookup hostname
This command should come back with the following information
similar. Note that this example is implementation specific. You may need
to talk to your System Administrator for these details on your platform:
Server: DNS Server Fully Qualified Domain Name (FQN)
Address: DNS Server IP Address
Name: Hostname Fully Qualified Domain Name
Address: Hostname IP Address
If the server is not registered or is misconfigured in DNS your
response may look similar to the following response:
DNS Server FQN can not find hostname. The host you tried to resolve:
Non-existent domain.
You will need to consult with your network administrator to ensure that
the hostname is resolved by DNS or system hosts files.
- If the above step was successful, then verify that the client and
server are running the same version of WebSphere and the Java™ SDK. If the
server is running WebSphere Application Server V4.0.7, then the client
should also be at V4.0.7. The product.xml files you have
sent show that both Server installations are running V4.0.7, please
confirm that the CSCX0424 box does not have a seperate installation of the
console, if it does, it will have an additional product.xml for the
standalone admin console install that would then need to be checked for
the version.
To verify that client and server are at the same JDK levels, perform the
following command in the install_root\java\jre
directory:
./java -fullversion
- Make sure the bootstrap port is available before invoking the Admin
Console. Information on what ports are in use may be obtained by running
the "netstat" or "netstat -a" command from the operating
system level command window. Is there a firewall between the 2 servers? If
so ensure you can get through the firewall by pinging USCSCDVE5 from
CSCX0424.
- Are you attempting to start the administrative console as root or
non-root user? If you are running the administrative console as a non-root
user, you need to change the ownership of the following directories and
files to the user and group that you will use to run the console:
install_root/bin
and
install_root/properties/sas.client.props
- Check the /etc/resolv.conf file does it have the proper hostname
listed? If not change it. This requires a recycle of the physical box for
the change to go into affect.
- Still not resolved? Then it's time to open a PMR. Please work through
MustGather: Administrative console problems for V4.0
and V5.0, then open a PMR so that we may assist you further.
|
|
|
|
|
|
|