-
Bug
-
Resolution: Done
-
Critical
-
5.0.0.Alpha4
-
None
When creating a configuration from scratch using an embedded server like this :
embed-server --admin-only --empty-config --server-config=sasl-upgrade.xml --remove-existing
Then configure the minimal extensions :
batch /interface=management:add(inet-address=${jboss.bind.address.management:127.0.0.1}) /interface=public:add(inet-address=${jboss.bind.address:127.0.0.1}) run-batch /socket-binding-group=standard-sockets:add(default-interface=public,port-offset=${jboss.socket.binding.port-offset:0}) batch /socket-binding-group=standard-sockets/socket-binding=management-http:add(interface=management,port=${jboss.management.http.port:9990}) /socket-binding-group=standard-sockets/socket-binding=management-https:add(interface=management,port=${jboss.management.https.port:9993}) run-batch batch /extension=org.jboss.as.logging:add /extension=org.wildfly.extension.core-management:add /extension=org.wildfly.extension.elytron:add /extension=org.jboss.as.jmx:add /extension=org.wildfly.extension.request-controller:add /extension=org.wildfly.extension.discovery:add /extension=org.wildfly.extension.security.manager:add run-batch
Then execute the 2 following scripts :
batch --file=/home/ehsavoie/galleon-scripts/configure_elytron.cli
batch --file=/home/ehsavoie/galleon-scripts/configure_realms.cli
Then it will fail with the following error :
Failure:
Since those services are added at boottime only by the ElytronAdd handler we shouldn't fail if we are already in a reload-required or admin-only mode.
