Rich client login failure

If the rich client login fails because the services tier cannot be reached, you can troubleshoot several possible causes.

Symptoms

The client login failure can be identified with the following information:
  • The stack trace from the client does not include the message Trace from server.
  • The stack trace shows that the root cause of the exception is a socket connection error.
  • The host name and port number are included in the error message.
  • A RegistrationHelper exception is included in the error message.
Stack traces and error messages vary depending on the situation. A connection failure might be identified with an error message about network connection, such as "Could not connect to server" or "port out of range." A connection failure might also be revealed in a stack trace that is similar to the following example: 
Exception type: javax/security/auth/login/LoginException
Exception message: Could not connect to server [green3] on port [9081].
Exception stack trace:
javax.security.auth.login.LoginException: 
  Could not connect to server [green3] on port [9081].
	at com.ascential.acs.security.auth.client.AuthenticationService.getLoginException
  (AuthenticationService.java:978)
	at com.ascential.acs.security.auth.client.AuthenticationService.doLogin
  (AuthenticationService.java:355)
Caused by: com.ascential.acs.registration.client.RegistrationContextManagerException: 
  Caught an unexpected exception.
	at com.ascential.acs.registration.client.RegistrationContextManager.setContext
  (RegistrationContextManager.java:76)
	at com.ascential.acs.security.auth.client.AuthenticationService.doLogin
  (AuthenticationService.java:349)
Caused by: com.ascential.acs.registration.client.RegistrationHelperException: 
  Caught an unexpected exception.
	at com.ascential.acs.registration.client.RegistrationHelper.getBindingProperties
  (RegistrationHelper.java:694)
	at com.ascential.acs.registration.client.RegistrationHelper.getBindingProperties
  (RegistrationHelper.java:587)
	at com.ascential.acs.registration.client.RegistrationHelper.getBindingConfigProperties
  (RegistrationHelper.java:566)
	at com.ascential.acs.registration.client.RegistrationContextManager.setContext
  (RegistrationContextManager.java:173)
	at com.ascential.acs.registration.client.RegistrationContextManager.setContext
  (RegistrationContextManager.java:73)
	... 1 more
Caused by: java.net.ConnectException: Connection refused: connect
	at java.net.PlainSocketImpl.socketConnect(Native Method)
	at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:352)
	at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:214)
	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:201)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:368)
	at java.net.Socket.connect(Socket.java:526)
	at java.net.Socket.connect(Socket.java:476)
	at sun.net.NetworkClient.doConnect(NetworkClient.java:175)
	at sun.net.www.http.HttpClient.openServer(HttpClient.java:407)
	at sun.net.www.http.HttpClient.openServer(HttpClient.java:542)
	at sun.net.www.http.HttpClient.<init>(HttpClient.java:246)
	at sun.net.www.http.HttpClient.New(HttpClient.java:319)
	at sun.net.www.http.HttpClient.New(HttpClient.java:336)
	at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient
  (HttpURLConnection.java:858)
	at sun.net.www.protocol.http.HttpURLConnection.plainConnect
  (HttpURLConnection.java:799)
	at sun.net.www.protocol.http.HttpURLConnection.connect
  (HttpURLConnection.java:724)
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream
  (HttpURLConnection.java:1047)
	at com.ascential.acs.registration.client.RegistrationHelper.getBindingProperties
  (RegistrationHelper.java:677)
	... 5 more

Resolving the problem

To resolve the problem, apply one of the following solutions, depending on the cause of the failure:
Cause Solution
The client computer host file has an invalid host name or IP address entry. Update the client computer hosts file so that the server host name can be resolved from client.
The server listening port might be blocked by a firewall. Ensure that the application server TCP/IP ports are not blocked by the firewall.
The application server is not running. Ensure that the application server is running.
In a cluster environment, you did not specify the host name and port of the front-end HTTP dispatcher. If IBM® WebSphere® Application Server clustering is implemented within your installation, direct the client to the host name and port of the front-end HTTP dispatcher. (The default port is 80.) The client login will fail if you specify the Deployment Manager host name and port or if you specify the host name and port of a single cluster member.
You changed a WebSphere Application Server port or modified the host file on the system, but you did not restart WebSphere processes after making the change. In a stand-alone (non-cluster) environment, restart IBM WebSphere Application Server.

In a cluster environment, restart the cluster.