Description of problem:

When the security realm is configured to use SSL certificate and the given keystore doesn't exist on filesystem it throws "alias not found in keystore". What is actually true, but it would be more user-friendly if exception will be more specific like "keystore not found".

Version-Release number of selected component (if applicable):


How reproducible: Everytime


Steps to Reproduce:
1. Configure your ManagementRealm to use SSL certificate.
2. Provide path to keystore which doesnt exist on filesystem
3. Start the EAP

Actual results:

17:31:00,570 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.server.controller.management.security_realm.ManagementRealmHTTPS.key-manager: org.jboss.msc.service.StartException in service jboss.server.controller.management.security_realm.ManagementRealmHTTPS.key-manager: JBAS021012: Key store entry not found for alias: appserver
	at org.jboss.as.domain.management.security.JKSKeystore.load(JKSKeystore.java:119)
	at org.jboss.as.domain.management.security.JKSKeyManagerService.start(JKSKeyManagerService.java:100)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_25]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_25]
	at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_25]


Expected results:

Should throw "keystore not found" exception.