The repository cluster settings (cluster-name, cluster-stack, cluster-config, cluster-locking) in the jboss subsystem are not properly evaluated during Wildfly startup. The clustering settings don't find their way into the repository configuration document and it's not possible to enable the ClusteringService. I've tested in domain mode, but assume it also affects standalone mode.

As a local workaround I've moved the cluster initialization code block in method performRuntime in class org.modeshape.jboss.subsystem.AddRepository in front of the "new RepositoryConfiguration(configDoc, repositoryName);" statement, so that configDoc already contains the parsed clustering settings when the RepositoryService is initialized.