"jhowell(a)redhat.com" wrote : This is in relation to https://jira.jboss.org/jira/browse/JBMESSAGING-1274 | But the problem is by the point they get the duplicate peer id message, the database is already hosed. Wouldn't be easier to avoid the database on HSQL from being damaged than making any substantial re-engineering or refactorings on JBM 1.4. IMO Changing the ServerPeerID on JBM 1.4 from an Integer to a String is technically possible but is unlikely to be done. That would change all the testcases on clustering, it would require extensive testing, for the cost of something that won't ever be used in production. In other words, it would diverge all of us from JBM2. We need to avoid the temptation of creating something that would look like a JBM 1.5. If you avoided the DB from being corrupted as you're saying, the user would just have to restart the server with the correct ID. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4180871#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...