[ http://jira.jboss.com/jira/browse/JBMESSAGING-854?page=all ] Ovidiu Feodorov closed JBMESSAGING-854. --------------------------------------- Resolution: Done Note: A clustered JBM configuration needs a production-grade database to function correctly and the default JB5 HQSLDB database is not one of them. In order to avoid introducing dependencies on drivers that are not available in the thirdparty directory the build script generates a clustered messaging configuration identical with a non-clustered one. This way, both "all" and "default" configurations start without errors, but "all" DOES NOT contain a truly clustered messaging instance. All clustered configuration files are available in the source tree, and build-dist.xml contains the correct sequence to create a valid clustered configuration, but that needs to be explicitly uncommented in order to work. So, in order to get a truly clustered confguration, you need to: 1. Uncomment the following sequence in build-dist.xml (and delete the mock one) 2. Add a valid mysql driver in server/all/lib <!-- This would be the "clustered" configuration. However, because we have a dependency on MySQL, we're actually not deploying a 'true' clustered configurtion just yet ... --> <!-- <copy todir="${install.all.deploy}" file="${_module.output}/etc/deploy/clustered/jms-ds.xml"/> <mkdir dir="${install.all.deploy}/messaging"/> <copy todir="${install.all.deploy}/messaging"> <fileset dir="${_module.output}/etc/deploy/common"> <include name="*-service.xml"/> </fileset> <fileset dir="${_module.output}/etc/deploy/clustered"> <include name="*-service.xml"/> <include name="mysql-ds.xml"/> </fileset> </copy> --> <!-- ... but we deploy a configuration identical to a "non-clustered" one. --> ... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira