Details
-
Bug
-
Resolution: Done
-
Major
-
None
-
None
Description
On slave DC security realm defined with only a trust store initialising the native interface raised the following error: -
[Host Controller] 16:24:15,297 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC00001: Failed to start service jboss.remoting.server.management: org.jboss.msc.service.StartException in service jboss.remoting.server.management: JBAS017113: Failed to start service
[Host Controller] at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStreamServerService.java:112) [jboss-as-remoting-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
[Host Controller] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
[Host Controller] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
[Host Controller] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30]
[Host Controller] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30]
[Host Controller] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
[Host Controller] Caused by: java.lang.IllegalStateException: JBAS017119: A security realm has been specified but no supported mechanism identified
[Host Controller] at org.jboss.as.remoting.RealmSecurityProvider.getOptionMap(RealmSecurityProvider.java:137) [jboss-as-remoting-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
[Host Controller] at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStreamServerService.java:101) [jboss-as-remoting-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
[Host Controller] ... 5 more
On a related note - if the native interface of the HC failed to start we should probably avoid starting the AS processes as we know there is nothing for them to connect back to.