I want to have a more secure management interface on our instance of WildFly CR1 by enabling https and disallowing http. But when I try this (note no "http" attribute on the socket-binding of http-interface):
<management-interfaces>
...
<http-interface security-realm="ManagementRealm" http-upgrade-enabled="true">
<socket-binding https="management-https"/>
</http-interface>
</management-interfaces>
I get an NullPointerException in the log. If I add the http attribute, it all starts up fine and I can connect successfully using the jboss-cli on the https port, but obviously I don't want that extra port open. The xsd has the "http" attribute as optional, which implies it should be possible to have just a https port.
Is this a bug?
That startup exception is:
[exec] 10:08:04,024 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss."remoting ".remoting-http-upgrade-service.http-management: org.jboss.msc.service.StartException in service jboss."remoting ".remoting-http-upgrade-service.http-management: Failed to start service
[exec] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.0.CR1.jar:1.2.0.CR1]
[exec] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
[exec] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
[exec] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
[exec] Caused by: java.lang.NullPointerException
[exec] at org.jboss.as.remoting.RemotingHttpUpgradeService.start(RemotingHttpUpgradeService.java:111) [wildfly-remoting-8.0.0.CR1.jar:8.0.0.CR1]
[exec] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.0.CR1.jar:1.2.0.CR1]
[exec] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.0.CR1.jar:1.2.0.CR1]
[exec] ... 3 more
