[ https://issues.jboss.org/browse/AS7-6539?page=com.atlassian.jira.plugin.s... ] Jeff Mesnil commented on AS7-6539: ---------------------------------- I don't have a good idea how we could transform the value of CLUSTERED depending on its children resource. When the hornetq-server resource is added, we don't have added the cluster-connection resource to make the decision yet. I think we can workaround the issue by setting CLUSTERED always to true. In HornetQ 2.2.x, this flag was used when the HornetQ cluster manager is started but iirc it does nothing if there are not cluster resources defined (cluster-connection, bridges, etc.) In other words, making sure the HornetQ server is always clustered might do no harm on legacy slaves which have not cluster resources. I'll check with the HornetQ team if that makes sense. -- 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