|
Problem(Abstract) |
Failure to pass the necessary security information when
connecting to a WebSphere® V5.0 Application Server from a client
application using an RMI connection might result in the following error:
com.ibm.websphere.management.exception.ConnectorException:
ADMC0017E: Could not create RMI Connector to connect to host <host
_name> at port 2809 |
|
|
|
Cause |
The full stack dump looks similar to the following
example:
at com.ibm.websphere.management.AdminClientFactory.
createAdminClient(AdminClientFactory.java:394)
at MyTestClient.main(MyTestClient.java:53)
---- Begin backtrace for nested exception
java.lang.reflect.InvocationTargetException:
java.lang.IllegalStateException: Error getting SecurityCurrent from the
ORB
at
com.ibm.ws.security.util.LoginHelper.getSecurityCurrent(LoginHelper.java:183)
at com.ibm.ws.security.util.LoginHelper.<init>(LoginHelper.java:65)
at com.ibm.ws.management.connector.rmi.RMIConnectorClient.
setupSecurityCredentials(RMIConnectorClient.java:126)
at com.ibm.ws.management.connector.rmi.RMIConnectorClient.<init>
(RMIConnectorClient.java:105)
at java.lang.reflect.Constructor.newInstance(Native Method)
at com.ibm.websphere.management.AdminClientFactory.
createAdminClient(AdminClientFactory.java:340)
at austin.MyTestClient.main(MyTestClient.java:53) |
|
|
Resolving the
problem |
Verify that the sas.client.props file is set up with the
necessary RMI security information, including:
- com.ibm.CORBA.loginUserid=<userid>
- com.ibm.CORBA.loginPassword=<password>
- com.ibm.CORBA.principalName=<userid>
1. Point to the sas.client.props file through the ConfigURL parameter when
you start the client.
For example:
java
-Dcom.ibm.CORBA.ConfigURL=<wasroot>\properties\sas.client.props
austin.MyTestClient <host> 2809 ...
|
|
|