|
Problem |
Trying to connect to DMGR using wsadmin over RMI fails.
wsadmin conencts to DMGR over SOAP, which eliminates network issues. After
enabling tracing on wsadmin, we can see this in the esadmin.traceout file
[5/3/05 11:30:23:386 IST] 4cc33af1 DefaultHostna d
java.net.UnknownHostException: dmgr
at java.net.InetAddress.getAllByName0(InetAddress.java:591)
at java.net.InetAddress.getAllByName0(InetAddress.java:560)
at java.net.InetAddress.getByName(InetAddress.java:469)
at
com.ibm.ws.naming.util.DefaultHostnameNormalizer.normalizeHostname(DefaultHostnameNormalizer.java:143)
at
com.ibm.websphere.naming.JndiHelper.normalizeHostname(JndiHelper.java:731)
at
com.ibm.ws.naming.util.WsnInitCtxFactory.normalizeUrl(WsnInitCtxFactory.java:1791)
at
com.ibm.ws.naming.util.WsnInitCtxFactory.parseBootstrapURL(WsnInitCtxFactory.java:1489)
at
com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:371)
at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:112)
at
com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:422)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:143)
at javax.naming.InitialContext.lookup(InitialContext.java:359)
at
com.ibm.WebSphereSecurityImpl.SecurityServerImpl.getSecurityServer(SecurityServerImpl.java:217)
at
com.ibm.WebSphereSecurityImpl.SecurityServerImpl.<init>(SecurityServerImpl.java:61)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:262)
cont................ |
|
Cause |
Error "UnknownHostException: dmgr" says its not
able to resolve the hostname "dmgr". Client has either defined 'dmgr'as
the hostname on the properties file or is invoking the wsadmin using
'dmgr' as the hostname. |
|
Solution |
Check the sas.client.props file for the process from which
you are invoking the wsadmin client. make sure the hostname is set to the
machine name which has the dmgr process running not the process name you
are trying to connect.
com.ibm.CORBA.securityServerHost=<machine_name>
If this is set to the correct value make sure are passing the correct
hostname during the wsadmin startup.
|
|