After logging into the BladeLogic Server Automation (BSA) Console or executing the BLCLI the folowing error message is reported:

Your session credential does not contain a usable application server URL. Cannot connect to "service.appsvc.bladelogic.blsess://<hostname>:9841"

or

You session credential does not contain a usable Application Server URL.
Errors were:
java.io.EOFException: Client disconnected due to EOF sent by application server
java.io.EOFException: Client disconnected due to EOF sent by application server

Depending on which scenario you fall into, you may also see a "Malformed URL" error message in the BSA Application Server log.
 

Legacy ID:KA316153

This error means the client had a problem connecting with the application server service.  Possible causes of this are that the authetication service's appserviceURL parameter is incorrectly auto-generated, the value is set incorrectly or the host is not reachable.

To debug this problem and identify the root casue perform the following steps:
1. Acquire credentials either using the NSH command "blcred cred -acquire" or through the BSA Console and selecting to save credentials during authentication.  If this step is performed through the Console authentication will appear to fail, but it is the connection to the appserver that fails as shown in the appserver log.

2. Run the command "blcred cred -list" (from the machine where the BSA Console is installed) or through the BSA Console view the session credential within the login panel.  To do this in the login panel, click Options and choose the Credentials tab.  Click on the credential listed and click View.
Observe the hostname listed for "appsvc.bladelogic".  Make sure this is the correct hostname (name of the appserver) and client can resolve the hostname (try to ping this hostname from the client).  Also check the port number listed for appserver service and make sure that is correct.

* If the hostname is incorrect, that means it was set incorrectly or not auto-generated correctly.  From the appserver run the command "blasadmin show authserver appservice" and confirm if "AppServiceURLs" is set to a value or empty string.  If the value is empty, then the value is auto-generated at authentication time.  One has the option to modify this option to set a specific value or set no value and a URL will be automatically generated.  For an auto-generated value run:

blasadmin set authserver AppServiceURLs ""

Or an explicit value can be set:

blasadmin set authserver AppServiceURLs "service:appsvc.bladelogic:blsess://<servername>:<port>"

This option is covered in detail in the BSA Administration Guide.  If the auto-generated hostname is incorrect this could be because the hosts file on the appserver has its own IP Address mapped to the incorrect hostname or DNS reverse lookup is not returning the correct hostname value.

* If the hostname is correct but the client cannot resolve the hostname, try adding an entry in the hosts file of the client so the hostname will resolve to the correct IP address.

3. If the information above is correct and the client can resolve the hostname, there could be other reasons that it is not working.  Check the appserver.log for any additional error information.  If you see an error about mismatching URLs, it could be that the appserver was resolving its IP address to its shortname but expecting a fully qualified hostname.  In this case you would see an error hinting at URL mismatch showing the expected and actual values. This can happen if the hosts file on the appserver has an entry which is correct but the hostname listed is either just the shortname, just the fully qualified hostname or both but in a certain order.  If only one name is listed, add the other, so the related entry looks like::
<IP Address> <FQDN> <shortname>.

If both the shortname and fully qualified name are present, try reversing their order.

4. If hostname resolution appears to be working correctly, also confirm the appserver is listening on the appservice port.  First verify the appservice port by running on the appserver:
blasadmin show appserver appsvcport

and then verify the port is being listened on by running this command from an NSH shell also on the appserver:
netstat -an | grep <appserver port number>

It should list one line as listening.  If you don’t see it stop the appserver service, make sure all corresponding processes are stopped (or kill them) and restart the appserver.  Run netstat again to make sure the service is running now. If the specified appsvcport is still not listening, check the application server log for this appserver to see if there were issues during startup.

5. Once it has been verified that the specified appsvcport port is listening on the appserver but the problem persists,  verify the client can connect to the specified appsvcport port.  To check this perform the following:

* ping appserver hostname from the client and confirm if there is a reply

* telnet to the appserver host/port from the client.
i.e.
telnet myappserver.bmc.com 9841

If this is successful telnet will connect.  Nothing will be printed on the screen but you will be able to type at least some characters and terminate the connection.. If the telnet command fails, make sure there is no firewall between the client and appserver which will prevent this communication.

If you are running an environment where there is a load balancer between the BBSA Console/NSH Clients and the Application Server, you are receiving this error and the above steps did not help resolve it, see KA288510  for information on configuring load-balanced environments.