[ https://issues.jboss.org/browse/AS7-5403?page=com.atlassian.jira.plugin.s... ] Joe Wertz commented on AS7-5403: -------------------------------- The basic problem is that the modcluster subsystem cannot start without certain values in the mod-cluster-config being configured. However, the mod-cluster-config can't be set up until there is a subsystem. The composite operation works because the subsystem does not attempt to start until after the mod-cluster-config is set up. I've found a few solutions, but the best seems to be this one. 1) Start the modcluster in a disabled mode. Adding a new attribute to /subsystem=modcluster:add(), 'enabled', and defaulting it to 'false', would allow the subsystem to be installed. Then the user could go into the mod-cluster-config and set up whatever they wanted, and go back and start the subsystem service once the setup is complete. This creates a small hassle, because the user has to go back and manually activate the subsystem after it's installed and configured, but it allows the user to configure the subsystem to their liking. Thoughts? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira