Clustered hypersonic configuration is causing problems for customers -------------------------------------------------------------------- Key: JBMESSAGING-1274 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1274 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.SP3.CP02, 1.4.0.SP3_CP01, 1.4.0.SP3 Reporter: Jay Howell Assigned To: Tim Fox When using the configuration for clustered hypersonic, you end up with the following problems... ------------------------------------------------------------------------------------------------------------------------------------------ 1. If you start two nodes with the same peer id, you get a failure. You say oh yeah I have to change the peer id. You change it and you get errors because the db has already been written to with the original peer id. This only occurs with clustered hypersonic becuase the two databases are separate.. 2. Failover does not happen correctly if you are using hypersonic, due to the fact that it's not a shared database. 3. I understand that this presents a delima because the default configuration(production) is a clustered configuration. So the configuration that needs to be shipped is a clustered, hypersonic implementation. Possible fixes include ----------------------------------- 1. Make the production configuration have a default implementation of Hypersonic(non-clustered). 2. Have the peer id auto generated so that users don't have to go in and change configuration prior to startup(this will prevent number #1 above). -- 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